Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=506720 --- Comment #7 from Denys Vlasenko <dvlasenk@xxxxxxxxxx> 2009-06-22 10:31:01 EDT --- Re static linking: busybox is a rescue package thing. It is useful when dynamic libraries are busted (think rm -rf /lib). Also, busybox is used when it's critical to minimize the size. glibc really is not caring about code size anymore. I don't know where exactly busybox is used in Fedora, but in above two cases people usually use statically linked busybox. Re static linking to another C library: uclibc can be configured and built as a dynamic library. What is the Fedora policy on this? Are alternative libc's allowed? BTW, in effect we already have two libc's on x86_64: 32-bit and 64-bit glibc have different ABIs and live in different directories. Adding more libc's boils down to selecting a directory for them (I don't know, /lib-i[456]86-uclibc?) -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review