Bug#527993: Module::Build::Compat's generated Makefile doesn't remove the Makefile in the distclean target

Niko Tyni ntyni at debian.org
Wed May 27 19:51:37 UTC 2009


On Mon, May 25, 2009 at 12:43:07PM -0700, Ryan Niebur wrote:
> On Mon, May 25, 2009 at 10:02:05AM +0300, Niko Tyni wrote:
> > 
> > If the change is not Debian-specific, it would be best to get it into
> > Module::Build upstream first.
> 
> It's been committed upstream:
> http://svn.perl.org/viewvc/modules/Module-Build/trunk/lib/Module/Build/Compat.pm?r1=12790&r2=12789&pathrev=12790

Thanks.

Earlier you wrote:

> libmodule-build-perl will be uploaded with this patch once perl-modules
> is patched.

and

> I didn't send it upstream first because I didn't want people to update
> to that new version and then not notice bugs in their packages that
> people using the version from perl-modules would. I will send it
> upstream now.

Could you please elaborate a bit? Do you expect this change to break
current Debian packages?

Normally, I'd expect that the change would go in libmodule-build-perl
first, and if it's needed for a significant number of packages so that
having versioned build dependencies on the fixed libmodule-build-perl
package would be a burden, it could possibly be backported to perl-modules
too.

If there's a risk of breaking something, it should be easy to run archive
test rebuilds with the change in a separate libmodule-build-perl package
(using the sbuild --add-depends or the pbuilder --extrapackages flag.)

Sorry if I'm sounding reluctant; I just think that a conservative
approach is better for the perl core packages particularly when bugs
can easily be worked around with a separate packaged newer version.

Cheers,
-- 
Niko Tyni   ntyni at debian.org






More information about the Perl-maintainers mailing list