Re: [Refdb-devel] RefDB-perlmod packaged as refdb-lib
Status: Beta
Brought to you by:
mhoenicka
From: David N. <dav...@sw...> - 2006-08-21 16:40:24
|
Hi St=E9phane, > I think it would be consistent to name your package=20 > libperl-refDB-perlmod instead of refdb-lib, to be in agreement with=20 > debian policy (to tell the thrut, i don't know what is the correct=20 > policy for perl modules in debian). Section 4.2 of the Debian Perl Policy ('Module Package Names', accessed=20 at=20 <http://www.debian.org/doc/packaging-manuals/perl-policy/ch-module_packag= es.html>),=20 states: "Perl module packages should be named for the primary module provided. The naming convention for module Foo::Bar is libfoo-bar-perl. Packages which include multiple modules may additionally include provides for those modules using the same convention." If one were to apply this naming scheme to RefDB-perlmod the result=20 would 'librefdb-perlmod-perl'. Because of the repeated text string=20 'perl' this name would be faintly ridiculous. In any event, the name=20 'refdb-perlmod' does not reflect any of the modules inside the=20 distribution -- it is simply a name Markus selected to call his=20 collection of modules. The policy claims the deb package should be based on the name of the=20 primary module. In my opinion you cannot select one of the modules in=20 the RefDB-perlmod archive as a primary one. They each serve a unique,=20 important function. In my opinion, therefore, the Policy does not apply = to the naming of this package. I considered myself free to pick a=20 meaningful name and believe I have done so. This package could be viewed as a library and so I could have called it=20 'librefdb'. I did not for two reasons: it is not a real library in the=20 common use of the term, and I wanted the refdb packages to appear close=20 together in package managers (i.e., the alphabetical order). Incidentally, you may have noticed my naming of the libperl-term-clui=20 package violates section 4.2 of the Debian Perl Policy. The trend to=20 name packages 'libperl-foo-bar' rather than 'libfoo-par-perl' is one=20 that has become increasingly popular. In my opinion it is easy to see=20 why -- it is much easier to extract the package name from a quick glance = since the major parts of the module name are separated by hyphens. Regards, David. |