[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#221982: glibc's at fault here...



retitle 221982 Please put nss modules in /lib/nss/ (or something like that)
severity 221982 wishlist
reassign 221982 glibc
thanks

Please keep myself in the Cc list.

On Wed, Apr 21, 2004 at 02:03:33PM -0700, Jeff Bailey wrote:
> On Wed, Apr 21, 2004 at 10:10:43PM +0200, Jeroen van Wolffelaar wrote:
> 
> > glibc is misplacing libnss_* according to Andrew Suffield.
> 
> > Disclaimer: I don't know that these files do, I trust this to the
> > descretion of the glibc maintainers :).
> 
> It's all good.  Andrew's wrong in this particular case.  Those files are
> used to help glibc figure out things like how to read /etc/passwd and
> such.  These all are useful when /usr hasn't been mounted yet (and could
> potentially be required for mounting it off of a remote NFS volume)

Shouldn't it be in /lib/nss/ then? This is a good reason to not put it
in /usr/lib/<package>/, but, I don't see why it shouldn't be in
/lib/(nss|glibc-modules|whatever)/. These files are indeed no shared
libraries, which makes it unnessasary (and against FHS if you're reading
it in a certain way) to put them directly in /lib.

Kernel modules, which aren't shared libs either, are also placed in a
seperate directory. It is also consistent with how /usr/lib works, also
there shared object files are within subdirs.

If you, glibc maintainers, really think they should be in plain /lib,
please reassign to debian-policy to have an exception there (I can image
'historical reasons' could be a reason). But if historical reasons don't
prevent a move, it could be a target of sarge+1.

--Jeroen

-- 
Jeroen van Wolffelaar
jeroen@wolffelaar.nl
http://jeroen.A-Eskwadraat.nl



Reply to: