Re: lintian: binary-or-shlib-defines-rpath
On 09-May-2002 Steve Langasek wrote:
> On Thu, May 09, 2002 at 11:18:18AM -0300, Henrique de Moraes Holschuh wrote:
>> On Thu, 09 May 2002, Marc Haber wrote:
>> > >Yes, for libraries. Plugins may use/need rpath.
>
>> > What exactly is the definition of a plugin in this context?
>
>> dynamic objects used/usable *only* by a certain program/library. E.g. the
>> apache plugins (plugin for app), the SASL plugins (plugin for a library);
>> Also linked at runtime using dlopen() or something like that. IMHO anyway.
>
> This does not follow. If it's a plugin, you don't link against it, so
> rpath is irrelevant. If it's something you link against, it's a
> library, and policy requires that it go in one of the system paths:
> therefore, rpath is unnecessary.
>
depending on the plugin system, rpath may or may not be used. Either way rpath
is a non issue for plugins.
System libraries are not supposed to define rpath by policy and that is the
important point here.
--
To UNSUBSCRIBE, email to debian-mentors-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: