Package name
Hi list,
I'm trying to package argtable (http://argtable.sf.net). I'm wondering
about the names to give the package.
The package itself had two major life cycles. As such, the source
library is called "argtable2". As far as so version goes, it has version
4. Obviously, I will need to ad a "lib" at the beginning. At the moment,
I have this:
source package: argtable2
shared object: libargtable2-4
devel: libargtable2-4-dev
I'm having doubts about all choices, however:
Should the source be named "argtable"? It seems that upstream is not
particularly interested in maintaining the "1" series around, but one
never knows. They are clearly and utterly incompatible, however, and
there is some slim chance that someone will want to package "libargtable1".
Should the "dev" be named with the so version? The policy says it
should, but the "2" is really confusing here.
In general, I have a suspicion that the "2" was really meant by upstream
to mean what "soversion" means, and so the package should really be
named "libargtable4". This will be WAY too confusing for actual users of
argtable, however.
Your thoughts on the matter would be greatly appreciated.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html
Reply to: