On Wed, Aug 23, 2006 at 06:49:55PM +0800, ?????? (LI Xin) wrote: > ??? 2006-08-23?????? 13:36 +0300???Kostik Belousov????????? > [snip] > > > An idea which wasn't suggested yet is to install a renamed version (I > > > would suggest libbaseldap instead of libbsdldap or libldap_i, but I > > > don't really care about the name) and a link from the original name > > > (only the .so and .a, but not the .so.X) to the new name. This link > > > can be protected with a WITHOUT_LIBLDAP_LINK switch (or the other way > > > around... depending on what we want to achieve). This way it is > > > possible to link with the renamed lib in the base system, to use the > > > base system version of the lib in ports, and to use the lib from ports > > > if desired (a recompile of ports may be needed in the last case, yes). > > > > This will not work. bsdxml is used inside the system binaries. No binary > > links again expat and bsdxml simultaneously. Would such binary exists, > > it could experience problems. > > > > On the other hand, application using openldap from the ports has high chance > > loading nss_ldap (e.g., due to nsswitch.conf). If nss_ldap linked against > > renamed library, this would cause the crash. > > > > In fact, similar problem was fixed not so long time ago by Dag-Erling > > in the pam_ssh (duplicating existing symbols by the pam). > > Maybe we can help him to extract some necessary routines out of the lber > and ldap libraries, and make it an internal library (say, put into the > nss module rather than installing a separate .so file)? May be. Moreover, this module (and any nss module) shall export only symbols needed by nss interface, not polluting the global namespace of process.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:59 UTC