NFSv4-patched ACL lib dependencies

[Kevin Coffman]

Hmmm.  The default installation location for libnfsidmap today is
/usr/local/lib, and the distribution maintainers decide where it is
ultimately installed.  I was going to leave that alone and, by
default, install all the new libs in /usr/local/lib as well.

Separating out the install location for libnfsidmap_umich_ldap would
be fine by me.  If I can make the life of the distribution maintainers
easier by changing the defaults, I'm all for it.  I'm not sure exactly
how to achieve that.  Any hints welcome!

K.C.

On Wed, Jul 9, 2008 at 1:21 PM, Paarvai Naai <opensource3141 at gmail.com> wrote:
> Hi Kevin,
>
>> I _was_ planning to install all the libs in the same place. I should
>> know this but, is there any reason libnfsidmap_umich_ldap.so can't, or
>> shouldn't, be installed in /lib as well?
>
> Technically, I don't think it matters if you install
> libnfsidmap_umich_ldap.so in /lib versus /usr/lib.  You are using
> dlopen with the RTLD_NOW option which will cause dlopen to error
> immediately if /usr/lib is not mounted and the symbols required by
> libnfidmap_umich_ldap.so (namely ldap, kerberos, etc.) are therefore
> not found.
>
> However, I believe the general convention is that no libraries in /lib
> should have dynamic dependencies to libraries in /usr/lib.  Running
> "ldd /lib/*.so", I find that there are very few, if any, libraries
> that have dependencies to libraries in /usr/lib.
>
> Furthermore, I compared FC5 with FC8 and noticed something
> interesting.  Both have /lib/libnss_wins.so.2, a library from samba
> that dynamically is linked against libraries fom /usr/lib.  However on
> FC5 the symlink libnss_wins.so is found in /lib but on FC8 it is now
> in /usr/lib.
>
> Thoughts?
>
> Best regards,
> Paarvai
>
>