I recently mistacenly updated libaal but not reiser4progs. That resulted in the server to hang during the next reboot. Shouldn't boot critical packages be linked statically? PS: There is the static useflag. But that results in 200 other packages to be linked statically (e.g. evolution, cinelerra, etc). See: http://forums.gentoo.org/viewtopic-p-2565309.html#2565309
You may just set the static useflag for that specific package, see man portage to use correctly /etc/portage/package.use The bug is marked as invalid, please reopen it if you think that it isn't
(1) You are right, I could keep package.uses always up to date with all the packages I suspect of being critical. But I would need to know about things that just could happen. And every single user would need to do that job. (2) I could also add STATIC to make.conf which would also apply for about 200 other packages (including cows as evolution or cinelerra), which might not be the desired effect. (3) A more general approach would be to link boot and network critical packages statically by default (which would make gentoo more failproof by default). There should be a policy for doing that. (4) The STATIC useflag could also be reserved for only those critical packages, so adding it to make.conf wouldn't produce undesired side effects. I vote for option (3) or (4) on the long run. Sorry for reopening the bug. Close it again an I'm quiet. :)
current setup is fine ... forcing static linking on everything in /bin and /sbin only results in bloating / size
