use Perl

• Just to be clear (Score:1)

  by btilly (5037) on 2008.03.18 4:14 (#61659) Journal

  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?

  Reply to This

  • Re: (Score:1)

    by Alias (5735)

    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.
    • Re: (Score:1)

      by btilly (5037)

      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?
      • Re: (Score:1)

        by Alias (5735)

        Nope. "traditional" is quite sane.
        
        It's the other one, "passthrough" I think, that's conceptually broken in the same way.
  • Re: (Score:1)

    by Aristotle (5147)

    That is so that people can install the module any way they please

    If you were actually using pass-through mode, that would not be the case. The Makefile.PL that is generated in that mode invokes Build.PL to do the work, incidentally offering to recursively install Module::Build if necessary. Therefore such distributions cannot be installed without Module::Build.

    In contrast, the traditional mode you are in fact using generates a regular Makefile.PL that invokes ExtUtils::MakeMaker as per usual, so does