[HEADS UP]: OpenLDAP+nss_ldap+nss_modules separated patch and more (SoC)

Boris Samorodov bsam at ipt.ru
Tue Aug 22 09:01:22 UTC 2006


On Tue, 22 Aug 2006 17:53:53 +1000 Peter Jeremy wrote:

> On Tue, 2006-Aug-22 14:20:03 +0800, LI Xin wrote:
> >Would you please consider having the imported OpenLDAP to install shared
> >objects under alternative names?  It might be painful for users who
> >wants OpenLDAP installation from the ports collection (as OpenLDAP team
> >moves fast and fixes bug from time to time) if they get a same library
> >in /usr/lib...

> I'll take an opposing view:  If the two libraries are compatible, I
> believe they should have the same name.  LD_LIBRARY_PATH, rpath and
> ldconfig can be used to control the search path if a particular .so
> variant is desired.

Using LD_LIBRARY_PATH may break some progs. Ex., when using
linuxulator searching for the needed Linux libraries ends up with
finding the FreeBSD ones.

> One difficulty with changing the .so names is that (eg) configure
> scripts expect to find libraries under fixed names - if a package
> has 'foo' as a dependency, it will usually look for libfoo.{a,so}
> and generally won't have any way to say "use libfoo_i.{a,so} instead
> of libfoo.{a,so}".

Can't those packages be suffixed, say libfoo[_i].{a,so} or else?

> I'd also note that (eg) openssl exists in both the base system and
> ports without any obvious problems.

But using kerberos from ports with LDAP (having a kerberised host) is
a real pain. Not to say about upgrading that system.

Said that I'd like to show that the problem is complex one and it
would be great to find the best way to solve it.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve


More information about the freebsd-current mailing list