> I wonder if it would be worthwhile to live with the code duplication and
> namespace pollution and use libltdl in convenience mode instead of
> installable mode with slapd. That would basically cause slapd to use
> RTLD_GLOBAL, correct? It would resolve the issue with back-perl and
> also with back-meta, at the cost of namespace pollution only for slapd
> plugins and things they load.
For back-meta, never mind -- Howard Chu says that back-meta is violating
the module policy for slapd and they will want to change it upstream so
that it doesn't have the direct dependency on back-ldap.
That still leaves back-perl. Maybe we can convince Brendan to start
linking all modules (and the Perl interpretor) against libperl as of the
5.10 release that's coming soon?
Russ Allbery <email address hidden> writes:
> I wonder if it would be worthwhile to live with the code duplication and
> namespace pollution and use libltdl in convenience mode instead of
> installable mode with slapd. That would basically cause slapd to use
> RTLD_GLOBAL, correct? It would resolve the issue with back-perl and
> also with back-meta, at the cost of namespace pollution only for slapd
> plugins and things they load.
For back-meta, never mind -- Howard Chu says that back-meta is violating
the module policy for slapd and they will want to change it upstream so
that it doesn't have the direct dependency on back-ldap.
That still leaves back-perl. Maybe we can convince Brendan to start
linking all modules (and the Perl interpretor) against libperl as of the
5.10 release that's coming soon?
-- www.eyrie. org/~eagle/>
Russ Allbery (<email address hidden>) <http://