Re: RefDB-perlmod packaged as refdb-lib

David Nebauer a écrit :
> Hi Stéphane,
> 
>> I think it would be consistent to name your package 
>> libperl-refDB-perlmod instead of refdb-lib, to be in agreement with 
>> debian policy (to tell the thrut, i don't know what is the correct 
>> policy for perl modules in debian).
> 
> Section 4.2 of the Debian Perl Policy ('Module Package Names', accessed 
> at 
> <http://www.debian.org/doc/packaging-manuals/perl-policy/ch-module_packages.html>), 
> 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 
> would 'librefdb-perlmod-perl'.  Because of the repeated text string 
> 'perl' this name would be faintly ridiculous.  In any event, the name 
> 'refdb-perlmod' does not reflect any of the modules inside the 
> distribution -- it is simply a name Markus selected to call his 
> collection of modules.
> 
> The policy claims the deb package should be based on the name of the 
> primary module.  In my opinion you cannot select one of the modules in 
> the RefDB-perlmod archive as a primary one.  They each serve a unique, 
> important function.  In my opinion, therefore, the Policy does not apply 
> to the naming of this package.  I considered myself free to pick a 
> meaningful name and believe I have done so.
> 
> This package could be viewed as a library and so I could have called it 
> 'librefdb'.  I did not for two reasons: it is not a real library in the 
> common use of the term, and I wanted the refdb packages to appear close 
> together in package managers (i.e., the alphabetical order).
> 
> Incidentally, you may have noticed my naming of the libperl-term-clui 
> package violates section 4.2 of the Debian Perl Policy.  The trend to 
> name packages 'libperl-foo-bar' rather than 'libfoo-par-perl' is one 
> that has become increasingly popular.  In my opinion it is easy to see 
> 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.
> 
> 
Thnaks a lot for the clarification ;-)

I asked this bacause our perl policy is perl-<module name> and i did the 
perl module perl-RefDB-perlmod for refDB-perlmod package.

We may need a mode generic name (RefDB-???) but as you've stated there 
is no primary one.

Cheers,

Stéphane
-- 
Stéphane Téletchéa, PhD.                  http://www.steletch.org
Unité Mathématique Informatique et Génome http://migale.jouy.inra.fr/mig
INRA, Domaine de Vilvert                  Tél : (33) 134 652 891
78352 Jouy-en-Josas cedex, France         Fax : (33) 134 652 901

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642