Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

gnome-base/libgnome-2.14.1
gnome-base/libgnome-2.16.0
gnome-base/libgnomecanvas-2.10.2
gnome-base/libgnomecanvas-2.14.0
gnome-base/libgtop-2.14.6
gnome-extra/libgail-gnome-1.1.1
gnome-extra/libgnomedb-1.2.2
gnome-extra/libgsf-1.12.0
gnome-extra/libgsf-1.12.1
gnome-extra/libgsf-1.14.0
gnome-extra/libgsf-1.14.2

Please, remove the flag and always install both static and shared libraries...

http://marc.theaimsgroup.com/?l=gentoo-dev&m=116026024223024&w=2

libgtop is done.

I don't agree with installing static libraries always. I believe for most of
those a better solution is to just never install static libraries - if there is
no reason by a package to have a static version around, why do so?
I understand that f.ex pam wants to static link glib to work in root prefix
instead of /usr, but libgnome and others?...
Ultimately I have some ideas to have portage know about static libraries more,
that's that something to elaborate later in a different bug or medium.

Well, USE=static to enable or disable static library building and installation
is broken, no way around that.
If you don't feel like always installing both, only install .so, that you can
do.

For what it's worth, PAM does _not_ want static glib: a) it's pam_console
wanting that, and that's because RedHat knows not how to write something it
seems b) a static glib2 won't help because that would be non-PIC while
pam_console has to be PIC (shared module).

I'm slowly removing the static use flags.  We'll just do default installs, like
every other package (which should generally install both).

All fixed.