Paul Evans wrote: > The order of tests in dh_auto_configure goes: > if (-x "configure") ... > elsif (-e "Makefile.PL") ... > elsif (-e "Build.PL") ... > > This prevents dual ExtUtils::MakeMaker + Module::Build modules (e.g. > anything using Module::Build::Compat ) from working properly; the > Build.PL should be tested first. > > Furthermore, some XS-based modules have a configure script; even if this > is present, the Build.PL should still be run in preference.
I can't change the order that dh_auto_* test for build systems, since doing so can break packages that depend on the current order. This specific case has previously been discussed in this thread: http://lists.debian.org/debian-perl/2009/05/msg00017.html However, work is nearly complete on adding a --buildsystem option that allows specifying which system to use when multiple systems are present. > A similar problem occurs in dh_auto_build and dh_auto_install. In their > current order, the Makefile is preferred over the Build script - this > means if the Makefile is in fact running Build in passthrough mode, it > wno't be passed the MODULEBUILDRC parameter, as required to prevent > Bug 517423 reoccuring. In the buildsystems branch, we have changed it to consitently use Build. -- see shy jo
signature.asc
Description: Digital signature
