Perhaps something that you can do is use a templating system to generate both Makefile.PL and Build.PL from a common source so that you only have to change things once. :)

Update: After looking at things in more detail, I see that perhaps you don't need to use templates at all. Module::CoreList autogenerated its Makefile.PL by using Module::Build::Compat with the create_makefile_pl => 'traditional' option in Build.PL.

I noticed that Module::CoreList does this ... do any other distros do this?

Yes. In the early days of Module::Build, I provided a parallel but unconnected Build.PL, just to get a feel for Ken's shiny new module and how it worked. I kept them separate because I wanted people to be able to install my module even if Module::Build was broken (and it was often broken in those very early days).

Naturally, I was appalled by the horrific camel-like code duplication in two places, Makefile.PL and Build.PL, but was willing to endure this as a convenience to my users. :-)

Much to my surprise, the simple act of adding a new (and unrelated) Build.PL caused my module to fail ActiveState's automated build process because, at that time, if a distribution contained both a Makefile.PL and a Build.PL, the ActiveState auto-builder chose the Build.PL (and the current Module::Build at that time failed its Windows tests). That has since been changed, ActiveState's auto-builder now chooses Makefile.PL if both exist.

Oh, and after adding the new and unrelated Build.PL, I had to change:

WriteMakefile(
   NAME     => 'Acme::EyeDrops',
   VERSION  => '1.45',
);
[download]

WriteMakefile(
   NAME     => 'Acme::EyeDrops',
   VERSION  => '1.45',
   PL_FILES => {}
);
[download]

I'm considering adding a Build.PL from Module::Build.

Why? My impression is that Module::Build is usually something people switch to when they've had it with MakeMaker. But if you're considering keeping MakeMaker onboard that must not be your reason...

To answer your question, I think keeping a real Makefile.PL around is a great idea. I make frequent use of PREFIX and modules that don't support it are a real pain.

-sam

If I do parallel maintenance, I don't piss anyone off. :-)

Update: I noticed that Module::CoreList does this ... do any other distros do this?