in reply to Re: Do Pure Perl CPAN packages really need to use ExtUtils::Command::MM?
in thread Do Pure Perl CPAN packages really need to use ExtUtils::Command::MM?

Thanks. However, that is essentially option A: bite the bullet. It would have to go in every single test file and every single set up script. If I am going to use ExtUtils::Command::MM to back my makefile, I either need

  • Comment on Re^2: Do Pure Perl CPAN packages really need to use ExtUtils::Command::MM?

Replies are listed 'Best First'.
Re^3: Do Pure Perl CPAN packages really need to use ExtUtils::Command::MM?
by Anonymous Monk on Feb 18, 2011 at 05:05 UTC
    If I am going to use ExtUtils::Command::MM to back my makefile, I either need: A compelling argument for why a makefile backed by Module::Build is not good enough.

    Hmm, so you're writing your own Makefile (no .PL)? That is the worst of all solutions :) --Module::Build::Compat (see Module::Build users -- please use the "traditional" create_makefile_pl option) ++Module::Install

    A solution that does not require me to hardcode Find::Bin + use lib in file after file. Eliya has proposed one solution but there are still some outstanding portability questions

    Why is that a painful/unpleasant/unavoidable solution? You only have to do it once. You don't even have to do it manually :) You can make it part of your template or automate it

    There is even use inc 'Plagger'; which you can use outside of Module::Install

[reply]

      No I am decidedly NOT writing my own makefile. I want to use the 'small' option of Module::Build::Compat - that generates a makefile that is backed by Module::Build. There is no need to go splattering FindBin/use lib all over if you use Module::Build. That was option B. Give me a little credit here :-)

[reply]
        Give me a little credit here :-)

        Yup, you've sure picked the worst possible option -- passthrough is crap; Having no Makefile.PL is a million times better than passthrough

[reply]

In Section Seekers of Perl Wisdom