On Fri, 2007-08-24 at 08:24 -0400, Simon Raven wrote: > add --libdir=/lib to the ./configure run in debian/rules and it fixes > this. applications expect to see libnss_* to be in /lib, > not /usr/lib . also, this defeats the purpose of the software if /usr > happens to be mounted from NFS or on a separate local partition, or > other situations.
Do you have any references or use case for this? When I initially set up the package I investigated this and found no compelling reason to keep it in /lib. Glibc seems to be fine with NSS modules in /usr/lib (since some other modules do this). If /usr is unavailable (which Glibc also handles fine it seems) the changes are high that the LDAP server is also not available (yet) (either /usr isn't mounted yet because of networking or slapd hasn't started (resides on /usr). The only problem here I can see is if Glibc does not handle the appearance of a NSS module during the lifetime of a process (haven't checked this). Also placing the NSS module in /lib will not get you name resolution any earlier because nslcd (the connection daemon) is in /usr/sbin and uses libraries in /usr/lib. > footnote: also, please see the sed bug in the libnss-ldap package's > bug reports, seems this package suffers from this bug. this bug makes > the postinst fail miserably (poor thing, heh), making it fail to > install. I assume that you are referring to #375108. I have recently updated the postinst to be more resilient against the use of funky characters and have just made some other enhancements to handle any character that could cause problems with sed. These fixes will be in the upcoming release. -- -- arthur - [EMAIL PROTECTED] - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
