Re: Packaging a shared library

[Ron Rademaker <ron@wep.tudelft.nl>]

Here's the control file, so you can see what it's for:

Source: libsafe
Section: libs
Priority: optional
Maintainer: Ron Rademaker <ron@wep.tudelft.nl>
Standards-Version: 3.1.1

Package: libsafe
Architecture: any
Depends: ${shlibs:Depends}
Description:  Protection against buffer overflow vulnerabilities
 Libsafe is a library that works with any pre-compiled executable 
 and can be used transparently. Libsafe intercepts calls to 
 functions known as vulnerable, libsafe uses a substitute version 
 of the function that implements the same functionality, but makes
 sure any buffer overflows are  contained within the current stack 
 frame.

Ron Rademaker


On Mon, 12 Jun 2000, Josip Rodin wrote:

> On Mon, Jun 12, 2000 at 05:25:36PM +0200, Ron Rademaker wrote:
> > I'm making a debian package that contains 1 thing: a shared library, it
> > the first thing I'm ever packaging. Now lintian gives an error that
> > there's no shlibs, it also says stuff about it being intential and so. I
> > think I don't need this shlibs, but I want to make sure. There's no binary
> > that depends on the shared library and as far as I understood from the
> > packaging manual that's what this shlibs is for, right?
> 
> If it's a shared library, and nothing links to it, what's the point of
> packaging it? :) If it's a plug-in or something like that (hint: dlopen),
> then Lintian errors are spurious, as long as you put your .so file in a
> private directory, i.e. one that isn't in ld.so.conf.
> 
> -- 
> Digital Electronic Being Intended for Assassination and Nullification
>