Would it be smart to enable the use of static-libs on certain packages?
Or should it be considered as bloat in Gentoo/Sabayon?
How I see it:
At compile time if you enable static-libs it will copy all the needed
functions from external libs into its own binary blob.
Benefits:
- Lesser breakage
Dnia 11.06.2012 o 16:56 Joost Ruis joost.r...@sabayonlinux.org
napisał(a):
Would it be smart to enable the use of static-libs on certain packages?
Or should it be considered as bloat in Gentoo/Sabayon?
How I see it:
At compile time if you enable static-libs it will copy all the needed
I include some messages from #sabayon-dev that I think could be useful
for this subject:
scarabeus joost_op: by default static libs are useless, but they should
be provided in similar fashion like debug symbols
micia I agree with scarabeus
micia I'd be inclined not to use them :P
micia scarabeus,
While split-debug symbols have predictable paths (/usr/lib/debug),
static libs and headers don't.
This is a very good reason in favour of avoiding to hardcode stuff
like that in the Entropy codebase.
USE=static-libs is fine as it is. If a pkg requires foo[static-libs]
then it's fine to enable the
s:in favour of avoiding to hardcode:to avoid hardcoding:
better I think.
--
Fabio Erculiani
