On Thu, Nov 4, 2010 at 6:06 PM, Michael G Schwern <[email protected]> wrote:
> I would consider that a bug in MI::Cat. It should either have its own list > or > make use of MM->libscan($path). You should report that to MI::Cat. > Module::Install uses MakeMaker but it is its own thing that MakeMaker has > no > control over. > Sorry, just getting back to this. Yes, I think they are aware of the problems with M::I::Catalyst. And upgrade has been recently discussed. But, ignoring M::I::Catalyst for now... Is there any way to use something like PMLIBDIRS to copy in these extra directories, by chance? For example, if PMLIBDIRS => [ 'root' ] currently MM builds a tree like: blib/lib/AppName blib/lib/root But what is needed is for a Catalyst app is: blib/lib/AppName blib/lib/AppName/root So, it's close, but the destination paths end up wrong in the Makefile. Plus, some configuration files (and others) at the same level as Makefile.PL needs to end up in the top-level MyName dir. For example config.conf would need to end up in blib/lib/AppName/config.conf. BTW -- if I do set PMLIBDIRS => [ 'root' ] I still get problems with spaces in paths even with the most recent MM. Should the paths be quoted in the Makefile? $ perl -MExtUtils::MakeMaker -le 'print $ExtUtils::MakeMaker::VERSION' 6.56 $ make make: *** No rule to make target `root/static/build/media/press_releases/06438f8 6a97fc0fcc4a4fc3168a8b9bdcb_Product', needed by `pm_to_blib'. Stop. $ fgrep 06438f86a97fc0fcc4a4fc3168a8 Makefile root/static/build/media/press_releases/06438f86a97fc0fcc4a4fc3168a8b9bdcb_Product Service Launches Today.pdf \ root/static/build/media/press_releases/06438f86a97fc0fcc4a4fc3168a8b9bdcb_Product Service Launches Today.pdf \ $(INST_LIB)/root/static/build/media/press_releases/06438f86a97fc0fcc4a4fc3168a8b9bdcb_Product Service Launches Today.pdf \ root/static/build/media/press_releases/06438f86a97fc0fcc4a4fc3168a8b9bdcb_Product Service Launches Today.pdf $(INST_LIB)/root/static/build/media/press_releases/06438f86a97fc0fcc4a4fc3168a8b9bdcb_Product Service Launches Today.pdf \ Thanks, -- Bill Moseley [email protected]
