| 1 |
On Thursday, December 16, 2010 08:37:29 Thomas Kahle wrote: |
| 2 |
> To enable the USE flags 'static' and 'static-libs' sometimes one needs |
| 3 |
> to have all of the dependencies (and maybe there dependencies) linked |
| 4 |
> statically too. In this regard the 'static' use-flag is very different |
| 5 |
> from other use-flags in terms of its consequences and requirements. |
| 6 |
> What is the policy for ebuilds: Should they USE-depend on their |
| 7 |
> dependencies being built with static too? |
| 8 |
|
| 9 |
the USE=static usage is unfortunate, but it's the best we have so far. but |
| 10 |
USE=static can be thought of as a "leaf" flag ... i cant think of any reason a |
| 11 |
package would depend on any other being built with USE=static. |
| 12 |
|
| 13 |
USE=static-libs however probably needs consideration in every package that |
| 14 |
supports USE=static. which i think is probably what you're after. |
| 15 |
|
| 16 |
> If yes, there are cases where this falls short. How would one handle |
| 17 |
> e.g. http://bugs.gentoo.org/show_bug.cgi?id=341983 |
| 18 |
> |
| 19 |
> app-backup/bacula needs a static glibc further down the dep chain. |
| 20 |
> Seems like out of pm's control? |
| 21 |
|
| 22 |
glibc always installs its static libraries. so i dont see how it could cause |
| 23 |
a problem for any other package, static or otherwise. |
| 24 |
-mike |
Archives