It would be nice if Gentoo could be built without static libraries, or at least most applications in it. Pros: 1. on my Gentoo box (400 ebuilds installed) static libraries take up 60M of space 2. they are rarely needed, a tipical box needs only *libc and *curses to have both shared and static libraries 3. Solaris 10 is using no static libraries at all ;) And for most packeges this would be as simple as "configure --disable-static"...
(In reply to comment #0) > It would be nice if Gentoo could be built without static libraries, or at least > most applications in it. It would not be really that nice to remove save-your-ass rescue capabilities made possible thanks to building some stuff static. For the rest, we have "static" use flag, if you don't like it, don't use it. I have no idea to whom this bug should be assigned, portage guys please re-assign if you don't want it.
INSTALL_MASK="*.a" should cover this
I'm sorry to say it, but it is not sufficient. Currently Gentoo builds bash with static ncurses (a bad idea IMHO), ldconfig has to be statically linked and there is insmod.static, too. Also the INSTALL_MASK would break gcc. And openssh is using static openssl libraries, too. Just to mention a couple of exceptions.
This is not a portage bug. It's one of those bugs that have no home at the moment. It's about changes to general ebuild policy. Perhaps we need a new alias?
(In reply to comment #4) > This is not a portage bug. It's one of those bugs that have no home at the > moment. It's about changes to general ebuild policy. Perhaps we need a new > alias? This should IMHO be really discussed elsewhere (like gentoo-dev mailing list) etc.
ldconfig is provided by glibc and when it is built, it links against the glibc in the build tree, not against the glibc in / as for bash, if you had read the ebuild, you'll see that it has a workaround if statically linking against libnucrses failed
