Re: different package and source name
> Od: Don Armstrong > > I am preparing package from 'lv2-c++-tools' source. It is library so I > > called > packages 'lv2-c++-tools0' and 'lv2-c++-tools-dev' > > But I got this warning from lintian: > > W: lv2-c++-tools0: package-name-doesnt-match-sonames libpaq0 > > > > I renamed packages to libpaq0 and libpaq-dev. > > lv2-c++-tools contains at least three libraries; liblv2-gui, > liblv2-plugin, and libpaq; presumably you should be building separate > binaries and -dev packages for them all. > > You'll want to read the library packaging guide before continuing much > further. > > > My question is: Is it normal to have totally different name of > > source and packages or should be solved somehow e.g. ask upstream > > for renaming source? > > In general, a source package should build at least one binary package > with the same name. The major exception are libraries like this one. Thanks for help regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: different package and source name
On Thu, 29 Oct 2009, Jaromír Mikeš wrote: > Here is layout of files which are installed by 'lv2-c++-tools' > source (except of files which should be part of dev package) > /usr/lib/libpaq.so.0.0.0 > /usr/lib/libpaq.so.0 -> libpaq.so.0.0.0 These two should be in libpaq0 > /usr/lib/liblv2-plugin.a > /usr/lib/libpaq.a > /usr/lib/liblv2-gui.a These three belong in the -dev package; probably libpaq0. > /usr/bin/lv2soname > /usr/bin/lv2peg I didn't bother to check what these do, but most likely they belong in the -dev package as well. > Any idea how to spread them to more packages? I didn't check closely enough when I was glancing at the source package, and thought that it created shared libraries for liblv2-plugin and liblv2-gui. Since it doesn't, they don't belong anywhere else but the -dev package. Before going any further, you really, really, need to read the Library Packaging Guide which covers this kind of thing. Don Armstrong -- "There's nothing remarkable about it. All one has to do is hit the right keys at the right time and the instrument plays itself." -- Bach http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: different package and source name
> Od: Don Armstrong JM> > I am preparing package from 'lv2-c++-tools' source. It is library so I called JM> > packages 'lv2-c++-tools0' and 'lv2-c++-tools-dev' JM> > But I got this warning from lintian: JM> > W: lv2-c++-tools0: package-name-doesnt-match-sonames libpaq0 JM> > I renamed packages to libpaq0 and libpaq-dev. DA> lv2-c++-tools contains at least three libraries; liblv2-gui, DA> liblv2-plugin, and libpaq; presumably you should be building separate DA> binaries and -dev packages for them all. Here is layout of files which are installed by 'lv2-c++-tools' source (except of files which should be part of dev package) /usr/lib/libpaq.so.0.0.0 /usr/lib/liblv2-plugin.a /usr/lib/libpaq.a /usr/lib/liblv2-gui.a /usr/bin/lv2soname /usr/bin/lv2peg /usr/lib/libpaq.so.0 -> libpaq.so.0.0.0 Any idea how to spread them to more packages? thanks for help mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: different package and source name
On Mon, 26 Oct 2009, Jaromír Mikeš wrote: > I am preparing package from 'lv2-c++-tools' source. It is library so I called > packages 'lv2-c++-tools0' and 'lv2-c++-tools-dev' > But I got this warning from lintian: > W: lv2-c++-tools0: package-name-doesnt-match-sonames libpaq0 > > I renamed packages to libpaq0 and libpaq-dev. lv2-c++-tools contains at least three libraries; liblv2-gui, liblv2-plugin, and libpaq; presumably you should be building separate binaries and -dev packages for them all. You'll want to read the library packaging guide before continuing much further. > My question is: Is it normal to have totally different name of > source and packages or should be solved somehow e.g. ask upstream > for renaming source? In general, a source package should build at least one binary package with the same name. The major exception are libraries like this one. Don Armstrong -- What I can't stand is the feeling that my brain is leaving me for someone more interesting. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
