request for comments on code for ExtUtils::MY overrides

[David Christensen]

makemaker@perl.org:







    http://search.cpan.org/~dpchrist/Dpchrist-Module-1.026/


Recently, I've been using CPAN testers to help squash the bugs:

    http://www.cpantesters.org/distro/D/Dpchrist-Module.html


So far, so good.  But, I know there are still issues:





3.  Some of the command-line tools invoked use GNU/Linux absolute paths.



http://www.cpantesters.org/cpan/report/1a09554e-fb48-11df-bb29-ad544afd17af


So, I've:

1.  Split the old module into two new modules:

        Dpchrist::ExtUtils::MakeMaker
        Dpchrist::Test

2.  Figured out how to daisy-chain MY::postamble() calls.

3.  Changed tool invocations to basename only.

4.  Ensured that there is only one *.pm file in each new module.





David

I've been using ExtUtils::MakeMaker for many years, it works well, and I like it. I've heard of Module::Install and Module::Build, but I'm of the mind "if it ain't broke, don't fix it". About a year ago, I wanted to add some targets and rules to the Makefile generated by ExtUtils::MakeMaker::WriteMakefile() and I wanted to collect together some favorite test scripts. So, I STFW, RTFM, looked in books, etc., and came up with this: 1. By mixing two kinds of things in one module (overrides for ExtUtils::MY and favorite test scripts), the overall distribution name was a compromise. 2. I am worried that by blindly stepping on the MY::postamble() subroutine, I will break other modules that also use it (ExtUtils::MakeMaker::Coverage?). 4. The distribution contains two modules, and some CPAN tester systems get confused: I would appreciate any comments, criticisms, suggestions, etc., on the attached modules. (Dpchrist::Test uses Dpchrist::ExtUtils::MakeMaker, and vice versa.)

Dpchrist-ExtUtils-MakeMaker-1.004.tar.gz
Description: GNU Zip compressed data

Dpchrist-Test-1.004.tar.gz
Description: GNU Zip compressed data