Michael G Schwern wrote in perl.perl5.porters : > Once I moved Test::More to github a bunch of people asked if I planned on > doing the same with MakeMaker. The answer is yes. The ability for others to > fork their own copies and for me to easily pull in changes will be invaluable > for MakeMaker. > > Rather than just put the CPAN module on github, some folks suggested I instead > fork the perl repository and work from that. This would make keeping > MakeMaker in sync with p5p a whole lot easier. > > For a normal module the plan would be simple, stick it into ext/ and work from > that. But MakeMaker builds everything else and needs some special attention. > The key thing being that MakeMaker has to be installed into lib/ before the > rest of ext/ can build. > > I see two strategies: > > 1) Copy ext/ExtUtils-MakeMaker/lib/ into lib/ at some point early in the build > process. > > 2) Jigger the ext/ build process so MakeMaker gets built first and installed > into lib/
The first option looks more feasible, since the copying into lib is done via Makemaker-generated makefiles anyway. (IIRC) Moving MM in ext/ would be nice for another reason : currently lib/ExtUtils contains many modules from different distributions, and lib/ExtUtils/t tests from many distributions as well. So upgrading MakeMaker in the core demands a bit more care than necessary. > I've made a fork on github and copied MakeMaker into ext/ > http://github.com/schwern/perl/tree/ExtUtils-MakeMaker > > Could someone familiar with the Makefile do the necessary voodoo to implement > either of the above strategies?