This one time, at band camp, Russ Allbery said: > Russ Allbery <[EMAIL PROTECTED]> 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?
I honestly don't know if it makes sense or not. When this was brought up, several people advanced several theories about why it might be done this way, and there were as many theories as people. I'd be curious in the general case why perl is built that way. If it turns out that it can be built so that the binary is linked to libperl on all arches, linking the modules is fairly straightforward - changing MakeMaker to always link to -lperl should do it for all the binary modules. We'll need to trigger a massive binNMU afterwards, but that should be doable. Do you feel like getting the ball rolling with Bod ? Cheers, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature