Re: Naming policy for Perl modules (mass bug filing)

[Marco Túlio Gontijo e Silva <marcot@debian.org>]

Hi Bastien.

Excerpts from Bastien ROUCARIES's message of Ter Mar 23 05:47:19 -0300 2010:
> 2010/3/23 Ansgar Burchardt <ansgar@43-1.org>:
> > Hi,
> >
> > the Debian Perl Policy asks for packages for the Foo::Bar module to be
> > named libfoo-bar-perl [1].  Some packages do not adhere to this scheme:
> >
> >  opalmod               → libopal-perl
> >  gnuift-perl           → libgnuift-perl
> >  perl-mapscript        → libmapscript-perl
> >  perl-tk               → libtk-perl
> >  speedy-cgi-perl       → libspeedy-cgi-perl
> >  exactimage-perl       → libexactimage-perl
> >  perl-ifeffit          → libifeffit-perl
> >  rplay-perl            → librplay-perl
> >  nfqueue-bindings-perl → libnfqueue-perl
> >  perlmagick            → libimage-magick-perl
> 
> In this case perlmagick is the upstream name, but we could create an
> empty package  libimage-magick-perl that will depend on  perlmagick ,
> or the reverse if needed, but thename perlmagick should be kept due to
> upstream naming [1].

You can use Provides: for this, instead of creating an empty package.

Please reply to me also, since I'm not on debian-perl list.

Greetings.
(...)
-- 
marcot
http://wiki.debian.org/MarcoSilva