I'm using Dist::Zilla and creating a Plugin to replace what Module::Install::Catalyst does. By default all files in home are copied to blib (to allow installing) except the following patterns:
our @IGNORE = qw/Build Build.PL Changes MANIFEST META.yml Makefile.PL Makefile README _build blib lib script t inc .*\.svn \.git _darcs \.bzr \.hg debian build-stamp install-stamp configure-stamp/; I'm thinking of reversing that logic and having a Dist::Zilla plugin that *explicitly defines* what is copied. So, any file in home that match these patterns would be included: ^root$ ^Changes$ \.yml$ \.conf$ \.inc$ \.psgi$ Is there anything else that should be in that default list of patterns to include? And, of course, allow to add files/dirs to that list via dist.ini configuration: ; replaces [MakeMaker] [CatalystFiles] include = conf include = config.yml I'm still not convinced this is the best approach, though. Copying the files when Makefile.PL runs always seems a bit of a kludge -- compared to, say, having "make" copy the files like a normal Makefile. And one could argue that these files and directories should go into "share" in the distribution and then get installed as File::ShareDir expects (i.e. have Catalyst::Utils::home() use dist_dir( $c->config->{name} ) ). But, that's kind of a big change. Anyone have thoughts on the that? -- Bill Moseley mose...@hank.org
_______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/