2010/3/23 Ansgar Burchardt <ans...@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]. [1] http://www.imagemagick.org/script/perl-magick.php Bastien -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/195c7a901003230147u22d479abxa7889a98e9e63...@mail.gmail.com
