Nomeclator of plugins
Hi, I think I have not seen it in the Debian policies. I have a dual role in one application: developer and co-maintainer. I would like to ask one question that fits in both. I'm in the bulmages project. It's a big piece of software with several applications with libs and plugins. It's a cmake build project. The plugins we have are lib.so. I add the properties (soname and version) to the plugins as the project main properties. The packages consist in several packages, etc. Now, we have a guy that it's packaging in Suse. First of all, he had to make some patch because the suse robot builders was more strict and didn't let him to build the package if some warning were done. We never receive any messages from that king [2]. The second, and it's my main question is about the nomenclature of the plugins. The guy says that the Suse force to create a package -dev if you have this kind of things (.so and symbolic links -.so.x.y.z). But I did a package for some .so (-dev) of the software, but not for all. Do we have a similar rule? Regards, Leo [1] http://developer.berlios.de/projects/bulmages/ [2] now the package is broken and I'm working in a new version with upstream ... -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Nomeclator of plugins
In 200907221847.44193@alaxarxa.net, Leopold Palomo-Avellaneda wrote:
I think I have not seen it in the Debian policies. I have a dual role in
one application: developer and co-maintainer. I would like to ask one
question that fits in both.
I'm in the bulmages project. It's a big piece of software with several
applications with libs and plugins. It's a cmake build project. The
plugins we have are lib.so. I add the properties (soname and version)
to the plugins as the project main properties. The packages consist in
several packages, etc.
The second, and it's my main question is about the nomenclature of the
plugins. The guy says that the Suse force to create a package -dev if you
have this kind of things (.so and symbolic links -.so.x.y.z). But I did a
package for some .so (-dev) of the software, but not for all. Do we have a
similar rule?
Something like that.
(IANADD)
A library package should install lib$SO_NAME.so.$SO_VERSION and be called
lib$SO_NAME$SO_VERSION.
The -dev package for that library should Depend on the library package,
install lib$SO_NAME.so as a symlink to the actual library (provided by the
library package), and be called lib${SO_NAME}-dev.
This allows multiple (major) versions of the library package to be
installed, so that package with binaries that haven't made the transition
can still run and Depend on the only version.
You might even consider making the SO_VERSION part of the lib*-dev package
name.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
b...@iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/
signature.asc
Description: This is a digitally signed message part.
Re: Nomeclator of plugins
On Wed, Jul 22, 2009 at 03:02:19PM -0500, Boyd Stephen Smith Jr. wrote: In 200907221847.44193@alaxarxa.net, Leopold Palomo-Avellaneda wrote: I think I have not seen it in the Debian policies. I have a dual role in one application: developer and co-maintainer. I would like to ask one question that fits in both. I'm in the bulmages project. It's a big piece of software with several applications with libs and plugins. It's a cmake build project. The plugins we have are lib.so. I add the properties (soname and version) to the plugins as the project main properties. The packages consist in several packages, etc. The second, and it's my main question is about the nomenclature of the plugins. The guy says that the Suse force to create a package -dev if you have this kind of things (.so and symbolic links -.so.x.y.z). But I did a package for some .so (-dev) of the software, but not for all. Do we have a similar rule? Something like that. No, nothing like that. (IANADD) A library package should install lib$SO_NAME.so.$SO_VERSION and be called lib$SO_NAME$SO_VERSION. Except that these aren't regular shared libraries, they're dynamically loaded plugins. Leopold: no, Debian has no requirement that every shared object have a -dev package associated with it (see the many and various Apache module packages -- I wonder how SuSE deals with that hoary chestnut). However, you MUST NOT put your plugins directly into /usr/lib (or any other ld.so search path); instead, place them in something like /usr/lib/package/plugins and have the application look for them in there. - Matt -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
