Re: what are shared libs and what are not ...
On 07-Mar-2001 Ben Collins wrote:
> On Wed, Mar 07, 2001 at 06:14:08PM +0100, Othmar Pasteka wrote:
>> hi,
>>
>> while packaging modlogan i have to use overrides because modlogan
>> uses shared objects for its plugin system which are not shared
>> libs. but since there has to be a shlibs file for shared objects
>> under /usr/lib i get lots of lintian errors, i.e. policy
>> violations.
>
> Plugins should not go in /usr/lib/., but should go in a subdirectory of
> /usr/lib.
>
> For example, PAM uses /lib/security/ and apache uses /usr/lib/apache/
>
> Do that, and lintian shouldn't complain. The problem here is that you
> are leaving these modules/plugins out at the will of the dynamic linker.
> Leaving them in /usr/lib/ makes ldconfig parse them, fills the
> ld.so.cache with useless libs, and thus adds overhead to the system's
> dynamic loader.
>
lintian WILL complains about any lib it finds, period. No has codified policy
to make lintian behave differently. I have asked on several occasions for
someone to put in writing what you say above and to no avail.
Reply to: