Guy Hulbert wrote: > On Mon, 2009-05-01 at 08:29 -0500, Adam Prime wrote: >> set up a basic >> (extendable and documented) configuration. > > AFAIK, Makefile.PL (ExtUtils::MakeMaker) is not designed to do this > although it is probably possible. > > It should be easy/ier with Build.PL (Module::Build, iirc) but I don't > think there is a standard method. > > You can do anything with Module::Install ... but it does not appear to > be as popular as Build.PL. > > It seems to be common practice to provide both Build.PL and Makefile.PL.
It's entirely possible, and indeed quite easy to do a "full install" with a stock Makefile.PL. I'm doing it now. I have a script that will take a bare O/S install, remotely drag in all of the dependencies, compile, merge in local customizations, install, archive the resulting image, and deploy it on multiple machines and flip the switch. In multiple architectures. The real issue is what, precisely, should a "generic default qpsmtpd" installation _do_ precisely? I view qpsmtpd as more of a platform, rather than a full application. One that requires a considerable amount of local customization before it's safe to flip the switch and turn it on. Doing installs via Makefile.PL works for me because what I produce and push out is a complete filtering front end, including all of the O/S stuff like cronjob adjustment/rc's, and a completely custom set of plugins.
