Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 241898 - Don't install static libraries for most GNOME packages
Summary: Don't install static libraries for most GNOME packages
Status: RESOLVED DUPLICATE of bug 241896
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: Lowest enhancement (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-14 08:53 UTC by Mart Raudsepp
Modified: 2008-10-14 09:26 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mart Raudsepp gentoo-dev 2008-10-14 08:53:48 UTC
Back when we were forced to remove USE=static for bogus policies, we ended up always installing static libraries due to yet another bogus policy. We should stop that, as there are absolutely NO consumers of the static libraries for 95% of the GNOME packages. They are maybe useful only for the C++ bindings, and glib (syslog-ng could use it, and it resides in /bin, while glib in /usr).

So we could either be exclusive of static libraries and have some variable that eclass looks to pass --disable-static, or inclusive and by default do that and have exceptions for glib and co. Or we just pass --disable-static for most packages in G2CONF separately.
What sounds like the best approach here?
Note that there is still some discussion to do about this on gentoo-dev as well, for making sure no-one is coming after us for not installing static libraries anymore because vapier said we must.

Shipping static libraries appears to be the primary reason why GNOME does not fit on the LiveCD anymore and they had to start using XFCE just because others in the team honored the USE=static + always install static libs statement (I'm not happy about that if you didn't figure yet :P).
Comment 1 Mart Raudsepp gentoo-dev 2008-10-14 09:26:48 UTC
I blame midori, apparently it re-posts when going back in history to the submit response

*** This bug has been marked as a duplicate of bug 241896 ***