> * The Hurd likes it a bit differently and more GNUish than GNU/Linux. > For example, we have another top level directory /hurd that is not > accounted for by the FHS, and we want to use /libexec at least for > the Hurd itself. That is not much of a huge technical issue, more > like a policy conflict. Will be taken up at the appropriate level > (hopefully FHS). > > Policy issue without lot of technical difficulties, at least for us. > The BSD people are going to care even more about /libexec if the > runtime linker is installed there, I guess! Please excuse my stupidity, but I don't really understand why the /libexec breaks anything. If it is made to be a symlink to /lib/libexec (or something like this), this wouldn't break the FHS. I must be wrong, so could you explain me what I misunderstood ? -- .''`. Josselin Mouette /\./\ : :' : josselin.mouette@ens-lyon.org `. `' joss@debian.org `- Debian GNU/Linux -- The power of freedom
Attachment:
signature.asc
Description: PGP signature