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 libXXXX.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 ...
Reply to: