"Scott K. Ellis" <[EMAIL PROTECTED]> writes: > On Sat, Jul 04, 1998 at 02:16:59PM -0400, Gregory S. Stark wrote: > > "Scott K. Ellis" <[EMAIL PROTECTED]> writes: > > > You have libpkg, it is included in the apt package. Run ldconfig. > > > > Uhm, shared libraries are supposed to be in separate packages with > > the soname version in their names. Packaging them in the same > > package as the binaries that use them is asking for trouble and > > violates policy. > > Nothing else uses the shared libraries (they are only used between > the various apt binaries). In addition, the package was originally > constructed to make it easy to download out of experimental and > install. Finally, I offer as precident, the dpkg package.
There are other examples, including two packages I maintain: mh (libmh) sp (libsp) nmh communicator4 My feeling was that if a shlib was not used nor ever likely to be used by any other packages, then it's ok to package it along with binaries. Reading policy, no such allowance is made. So am I and apt and dpkg etc all in fatal non-compliance? Can we loosen policy a little? -- .....A. P. [EMAIL PROTECTED]<URL:http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
