[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Naming guidelines question

On Fri, May 26, 2006 at 08:42:18PM +0300, Ville Skyttä wrote:
> And how about the rest of the guidelines which say that certain
> packages must be prefixed eg.  by perl-*, python-*, or be named like
> $appname-$plugin?  What about subpackages?

W/o backing up any side of the discussion: PIL (The python imaging
library) is either packaged as PIL or python-imaging. Similar for
PyGame, NumArray/Numerics and so on. I've often seen people comment on
not having been able to identify the python bits they were after.

What I really want to say is that upper/lowercase is the least of the
problems, there are other mappings performed that can be more
confusing or not to users/developers.

The suggestion to use normalized Provides (lowercase) should be
extended to more than capitalization. The normalized Provides should
conform to some strict guideline and be the ones used for dependencies
in other packages, and the core name of the package should be left to
the packager with the recommendation to match upstream conventions

Packagers win due to a normalized dependency system and packages have a
higher recognition value to users and upstream.
Axel.Thimm at ATrpms.net

Attachment: pgpYHKoR63DfY.pgp
Description: PGP signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]