static use flag
 

Hi,

To enable the USE flags 'static' and 'static-libs' sometimes one needs
to have all of the dependencies (and maybe there dependencies) linked
statically too. In this regard the 'static' use-flag is very different
from other use-flags in terms of its consequences and requirements.
What is the policy for ebuilds: Should they USE-depend on their
dependencies being built with static too?

If yes, there are cases where this falls short. How would one handle
e.g. http://bugs.gentoo.org/show_bug.cgi?id=341983

app-backup/bacula needs a static glibc further down the dep chain.
Seems like out of pm's control?

Has this been discussed on gentoo-dev earlier? Being new to devhood,
I'm looking for references.

Cheers,
Thomas


--
Thomas Kahle
http://dev.gentoo.org/~tomka/

static use flag
 

On Thursday, December 16, 2010 08:37:29 Thomas Kahle wrote:
> To enable the USE flags 'static' and 'static-libs' sometimes one needs
> to have all of the dependencies (and maybe there dependencies) linked
> statically too. In this regard the 'static' use-flag is very different
> from other use-flags in terms of its consequences and requirements.
> What is the policy for ebuilds: Should they USE-depend on their
> dependencies being built with static too?

the USE=static usage is unfortunate, but it's the best we have so far. but
USE=static can be thought of as a "leaf" flag ... i cant think of any reason a
package would depend on any other being built with USE=static.

USE=static-libs however probably needs consideration in every package that
supports USE=static. which i think is probably what you're after.

> If yes, there are cases where this falls short. How would one handle
> e.g. http://bugs.gentoo.org/show_bug.cgi?id=341983
>
> app-backup/bacula needs a static glibc further down the dep chain.
> Seems like out of pm's control?

glibc always installs its static libraries. so i dont see how it could cause
a problem for any other package, static or otherwise.
-mike