On 19/07/10 23:06, Thomas Bushnell, BSG wrote: >> * What's the reason for having a libmachuser / libhurduser be part of >> glibc? >> >> Is it for Roland's convenience, or is there a technical reason? Can >> we move it out of the glibc build process? >> > > Given the need for the libraries, they have to be built somewhere. Since > glibc needs to use these interfaces, you can't possibly have gnulibc without > them.
It would still be possible to move libhurduser to Hurd, though? That way you avoid the issue that if you add an RPC and want to use it in another part of Hurd, you need to add it, build glibc with the new Hurd installed, and then use it. The same applies if you want to use it from an independent project, with libhurduser in Hurd you would only need a new Hurd. Regards, Emilio
