Bug#557882: ITP: libextutils-manifest-perl -- utilities to write and check a MANIFEST file
Le Thu, Nov 26, 2009 at 12:12:35PM +0100, Xavier Oswald a écrit : On 19:54 Thu 26 Nov , Charles Plessy wrote: I just injected libextutils-manifest-perl in your SVN repository. Given the concerns I expressed above, I would like to see a green light before uploading to NEW… Seems well done, but I think you forgot the debian/* copyright holder in debian/copyright Le Thu, Nov 26, 2009 at 01:17:49PM +0200, Niko Tyni a écrit : On Wed, Nov 25, 2009 at 09:18:50AM +0900, Charles Plessy wrote: I intend to package the ExtUtils::Manifest Perl module. It is already packaged in the perl-modules packages, but in Lenny the provided version is too low to allow backports of one package of mine that would be fine otherwise. Have you checked if your package actually needs something from the newer ExtUtils::Manifest? It could be just a spurious dependency. Dear Xavier and Niko, thanks for your answers. The latest version of the BioPerl package really needs ExtUtils::Manifest; that was discussed on the upstream mailing list a couple of times. But actually ExtUtils::Manifest contains only one .pm file. As an ugly workaround, maybe I could try to add it to the bioperl backport source package and work out debian/rules so that it is recognised by Perl at build time in its path to search for packages. That would save the perl-modules package Provides, Replaces and Conflicts fields from getting one additional entry, and make one less package to manage in Squeeze, since as you noted well, it looks like its only use for the moment would be to help the backport of Bioperl. I will follow your recommendation on this issue. As for the debian/* copyright entry, I tend to omit it when I do not have the feeling that my contribution is complex enough to be coyrightable, but for the sake of consistency in the pkg-perl repository, I will add it if this package is not cancelled. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557882: ITP: libextutils-manifest-perl -- utilities to write and check a MANIFEST file
Le Wed, Nov 25, 2009 at 09:18:50AM +0900, Charles Plessy a écrit : I intend to package the ExtUtils::Manifest Perl module. It is already packaged in the perl-modules packages, but in Lenny the provided version is too low to allow backports of one package of mine that would be fine otherwise. My purpose is therefore to prepare a libextutils-manifest-perl package similar in design to libmodule-build-perl, which is also dually present in Debian, and then to submit a backport to backports.org after the package migrated in Testing. Please let me know if this would create problems or if more coordination is required with the perl-modules package. Hello Perl team I just injected libextutils-manifest-perl in your SVN repository. Given the concerns I expressed above, I would like to see a green light before uploading to NEW… Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557882: ITP: libextutils-manifest-perl -- utilities to write and check a MANIFEST file
On Wed, Nov 25, 2009 at 09:18:50AM +0900, Charles Plessy wrote: I intend to package the ExtUtils::Manifest Perl module. It is already packaged in the perl-modules packages, but in Lenny the provided version is too low to allow backports of one package of mine that would be fine otherwise. Have you checked if your package actually needs something from the newer ExtUtils::Manifest? It could be just a spurious dependency. My purpose is therefore to prepare a libextutils-manifest-perl package similar in design to libmodule-build-perl, which is also dually present in Debian, and then to submit a backport to backports.org after the package migrated in Testing. Do you mean a sid+squeeze package is only needed because of a backports.org policy to only accept packages in squeeze? That seems a bit backwards to me. Please let me know if this would create problems or if more coordination is required with the perl-modules package. We should add Provides: libextutils-manifest-perl Replaces: libextutils-manifest-perl Conflicts: libextutils-manifest-perl ( 1.56) into perl-modules if there's going to be a separate package too. Even if it ends up only in backports.org, the control entries don't hurt and they could be useful for upgrades. Please file a bug against perl about this if libextutils-manifest-perl is uploaded. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557882: ITP: libextutils-manifest-perl -- utilities to write and check a MANIFEST file
Package: wnpp Severity: wishlist Owner: Charles Plessy ple...@debian.org Package name: libextutils-manifest-perl Version : 1.57 Upstream Author : Andreas Koenig andreas.koe...@anima.de URL : http://search.cpan.org/~rkobes/ExtUtils-Manifest-1.57/ License : Perl Programming Lang: Perl Description : utilities to write and check a MANIFEST file Dear Perl team and Debian developers, I intend to package the ExtUtils::Manifest Perl module. It is already packaged in the perl-modules packages, but in Lenny the provided version is too low to allow backports of one package of mine that would be fine otherwise. My purpose is therefore to prepare a libextutils-manifest-perl package similar in design to libmodule-build-perl, which is also dually present in Debian, and then to submit a backport to backports.org after the package migrated in Testing. Please let me know if this would create problems or if more coordination is required with the perl-modules package. Here is a tentative description: ExtUtils::Manifest is a Perl module that provides a number of utilities to write and check a MANIFEST file. At present the list includes mkmanifest, manicheck, filecheck, fullcheck, skipcheck, manifind, maniread, manicopy, and maniadd. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
