Bug#66023: PROPOSAL] Treat plugins and shared libraries differently
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.
> 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)...
> 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.
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).
--
Digital Electronic Being Intended for Assassination and Nullification
Reply to: