Re: Bug#530615: ITP: libfile-temp-perl -- return name and handle of a temporary file safely
On Tue, May 26, 2009 at 11:05:35AM -0400, Jonathan Yu wrote:
> Niko's suggestion of using a description to alert users and other
> maintainers about the purpose for such a module is great, and I have
> no objection to that. Perhaps this is something we can consider in a
> broader sense to help our users decide. We have to keep in mind though
> that newer releases of perl-modules may mean that we'd have to remove
> that particular section, and isn't this essentially what
> debian/changelog is supposed to be for?
If the perl package catches up with the separately packaged version,
there's no point in having the two copies in the archive, so the separate
one should get updated or removed.
There are now lintian warnings for spotting this
and if perl-modules actually overtakes the separate package, they should
become uninstallable together due to the conflict declarations.
> Another question is.. If there is a bug with Module::Build that we
> need to fix, should a bug be filed against perl-modules (>= 5.10) or
> under libmodule-build-perl? We could upgrade our own version and apply
> our own patches, and just require that in B-D for modules where a bug
> in M::B is problematic. It's more difficult to get it fixed in
> perl-modules and subsequently require perl-modules (>= 5.10-11) or
IMO both packages should get their own clone of the bug, but the separate
package should normally be fixed first.
As it's easy to work around the bug in the perl package by installing the
separate fixed package, the best option for the former may well be to
wait until the fix arrives in Debian via the normal upstream way (CPAN ->
bleadperl -> maint-5.10 -> 5.10.x).
This depends on the nature of the bug of course. See for instance
#483144, where I opted to wait, and #494679, where that wasn't an option.
In the specific case of Module::Build, I see no problem in specifying
versioned build dependencies on a recent enough libmodule-build-perl
package. If the fix gets in perl-modules at 5.10.1, the lintian check
mentioned above will get triggered, and (assuming someone notices this)
the build dependency can later be changed to something like
perl-modules (>= 5.10.1) | libmodule-build-perl (>= X)
Niko Tyni firstname.lastname@example.org