> Miquel, could you please briefly explain what kind of features in > the new libc do you need, and what kind of breakage would happen > when using the old libc?
Older versions of glibc included the /etc/init.d/mountkernfs and /etc/init.d/devpts.sh scripts. The latest initscripts package includes a /etc/init.d/mountvirtfs script that takes over that functionality. glibc >= 2.3.2-12 doesn't include those scripts anymore. I don't think that script gets installed on Debian GNU/Hurd. And even if they did, they can't be run since they are GNU/Linux specific with their need for /proc... Newer sysvinits need to depend on a glibc >= 2.3.2-12. Since Debian GNU/Hurd doesn't use sysvinit, just depending on libc0.3 seems like a good enough solution I think, or just not listing libc0.3 at all (as it is now AFAIK). > Can you check for the required features using some sort of > configure script and refuse to build if the libc is not good > enough? Yes, using build-depends. But that is very hard because the glibc package is named differently on several architectures :( Aye, stupidity of the first degree with those nameing schemes I say! Can somebody enlighten me and tell me what the current ftp.debian.org as well as "experimental" package names are for glibc on both Hurd and kFreeBSD, what version they are and what direction development is taken ? The experimental archive has hacked version of packages that have quick hacks to get things running on Debian GNU/Hurd. I'm trying to work with you here, And we appericate it!
