Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I have several CPAN modules that use Module::Build and also use Module::Build::Passthrough to create a Makefile.PL. That is so that people can install the module any way they please, whether or not Module::Build is installed. They are all the simplest possible case - a single pure Perl module with no or minimal dependencies.

    Are you saying that going forward I will be unable to do this?
    • I'm certainly saying you SHOULDN'T use it, since it spawns a sub-CPAN client, which may well explode.

      If you have a simple module then you'd be far better off generating a compatibility Makefile.PL rather than a pass-through.

      The pass-through functionality would be best off being deprecated.
      • Huh. I just looked at one of my Build.PL scripts.

        use Module::Build;
        Module::Build->new(
            module_name => "Text::xSV",
            license => 'perl',
            create_makefile_pl => 'traditional',
        )->create_build_script;

        The Makefile.PL doesn't refer to Module::Build in any way.

        That isn't what you're deprecating, right?
        • Nope. "traditional" is quite sane.

          It's the other one, "passthrough" I think, that's conceptually broken in the same way.