On Thu, 2008-01-17 at 14:58 -0800, Russ Allbery wrote: > Tim Brown <[EMAIL PROTECTED]> writes: > > > I'm packaging OpenVAS and have the following problem. The upstream > > package for the component I am working on is called openvas-libraries, > > so I was initially going to package it as libopenvas. However, it > > contains two libraries, libopenvas and libopenvas_hg and I was getting > > complaints that libopenvas didn't match the SONAME (for > > libopenvas_hg.so), so I broke it down into one package per library (and > > a dev package for each) - libopenvas and libopenvas_hg. However I'm now > > getting complaints that the package name of libopenvas_hg is illegal.
> Multiple library packages are only useful if the libraries are going to > change independently (and probably only useful if applications that link > against the libraries may conceivably link to only one of them and not the > other). (or if the libraries can operate separately upon installation - e.g. plugins for libraries - because it helps keep the dependencies under control.) -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
signature.asc
Description: This is a digitally signed message part
