So this is my first post to the monestary, and I swear I've tried the search.
I am trying to do some extensive clean up of our code base and would like your input on some foundation things. The project is a set of retail web sites and some internal tools. And we are thinking of using RPM modules to deploy code to production.
Do you suggest ExtUtils::MakeMaker or Module::Build? Has Module::Build been accepted and widely used now? Is MakeMaker still the de facto standard?
In addition to the normal perl/pod in the lib dir, we have some config files and data files from other paths to be used during runtime and I would like the "make install" or "Build Install" to move into proper system locations.
It looks like Module::Build has some hooks for that, but I find it hard to believe that I would have to subclass the build object just to do this. Does MakeMaker have anything better?
Or am I approaching this completely wrong? I feel like many developers must have already run into this and found some elegant solutions.
Thanks a lot
In reply to MakeMaker or Module::Build by lagrasta
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |