Bug#66023: PROPOSAL] Treat plugins and shared libraries differently
On Thu, Jun 22, 2000 at 03:35:08PM +0200, Josip Rodin wrote:
> On Wed, Jun 21, 2000 at 06:14:17PM +0100, Julian Gilbey wrote:
> > I propose prepending text like the following to section 4.3.
> >
> > Shared libraries are .so files containing compiled
> > code that are loaded by the ld.so(5) library.
>
> That is ld.so(8) on my system.
Ditto. Actually, since we basically only use ELF nowadays, that
should probably be replaced by "ld-linux.so(8)".
> > They must always be installed in the directories listed
> > in ld.so.conf. (Applications may also have private .so files,
> > often called `plugins', which are stored `/usr/lib/program_name';
>
> ...and loaded using dlopen(3)...
Good point.
> > they are exempt from all the rules in this section, except that they
> > must not be installed executable).
>
> I agree with the spirit of this proposal, but the wording should be more
> explicit about what happens if the package wishes to add its directory into
> ld.so.conf. The Xaw library replacements do that, but it's not regulated by
> the Policy.
Yes, I agree, but that should be a separate proposal, I would guess.
Maybe file a bug report against ldso for an update-ldso-conf script.
> Maybe we should define the default directories that every ld.so.conf file
> should contain - /lib /usr/lib /usr/X11R6/lib - and mark every other
> directory as package-specific. The libc5-added directories,
> /lib/libc5-compat and /usr/lib/libc5-compat would need to be added as
> exceptions (which isn't a problem, since there aren't any more like these,
> and libc5 is dying out fairly quickly).
Again, let's discuss this first with the ldso maintainer.
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. J.D.Gilbey@qmw.ac.uk
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
Reply to: