Re: package naming
IMO the best name is the one that does the best job of expressing what it's
called without being so generic as to cause potential name conflict. I'd
personally go with libmetakit, with -dev, -tcl, -python if you split it up.
In general the version number isn't in the package name unless there's some
pressing need to be able to install multiple versions at the same time, so
hopefully libmetakit4 or 40 won't be necessary.
On Mon, Feb 12, 2001 at 04:30:32PM +0100, Ove Kaaven <firstname.lastname@example.org> spake forth:
> Are there any docs with guidelines on package naming? I need to package
> some dependencies, one of which is the MetaKit portable embedded database
> library (http://www.equi4.com/metakit/). The build process gives me
> libmk4.so.0.0.0, libmk4tcl.so.0.0.0, and optionally libmk4py.so.0.0.0
> (they don't seem to have considered library versioning in their
> "portability" or something). The upstream version is 2.0.1. So, what
> should I call this package?
> Alternatives seem to be:
> or maybe something else?
> (of course with a -dev package to go with it, not sure if I want to split
> up the tcl and python stuff into their own packages too, since I'm not
> particularly interested in this lib, it's just a dependency not in debian
> To UNSUBSCRIBE, email to email@example.com
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
Mike Markley <email@example.com>
GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084
Blast medicine anyway! We've learned to tie into every organ in the
human body but one. The brain! The brain is what life is all about.
- McCoy, "The Menagerie", stardate 3012.4