On 3/12/2012 12:43 AM, David Oswald wrote: >> Perhaps I should look (at some point) at moving some of the >> configuration logic out of Makefile.PL and into a CPP.pm.PL file for >> Inline::CPP. CPP.pm.PL could read the existing CPP.pm and write out >> the changes much like the way Makefile.PL does it, but under the >> direction of ExtUtils::MakeMaker instead of directly under >> Makefile.PL. I'm going to have to try this out, but I worry about make getting confused if X.pm.PL reads from, then writes to, X.pm. That would be my favorite way to organize things (not least because it wouldn't break the CPAN documentation system), but I'm not sure it'll work correctly. >> That reminds me, there's another solution to the OP's question. His >> module could be adapted to simply read a configuration file on >> startup, and that config file could be built at configuration/install >> time. Config::General could help to avoid rolling a new solution. I thought of that, but it seems inelegant. I'd much rather configure the PM directly during installation. I'm actually pretty excited about this mechanism; it's neat!
Michael
