Re^3: RFC - Module::Cooker (File::ShareDir::Install)

I'm not quite sure what you mean ... Module::Cooker places its data files under its own directory

Pretty much what I said, don't do that, use sharedir , sharedir is the "official" way ... perldoc/pod2html... will all find your "data files" and treat them as real perl modules ... because they live in the module tree and are named like modules ... you avoid that with sharedir , its why its the "official" standard :)

Also remember to consider version-ing or even theme-ing your template sets ...

Comment on Re^3: RFC - Module::Cooker (File::ShareDir::Install)

Replies are listed 'Best First'.
Re^4: RFC - Module::Cooker (File::ShareDir::Install) by boftx (Deacon) on Dec 02, 2013 at 08:57 UTC
I need to think on this. My gut is telling me that there is a reason that what you suggest would not work, but I can't put my finger on it. :) As to versioning/theming of the templates, that is something I had not thought of. I just assumed (yeah, I know) that using git to handle that for the distro was enough. It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.	[reply]
Re^5: RFC - Module::Cooker (File::ShareDir::Install) by Anonymous Monk on Dec 02, 2013 at 09:13 UTC
As to versioning/theming of the templates, that is something I had not thought of. I just assumed (yeah, I know) that using git to handle that for the distro was enough. Well, yeah, using git is enough for your purposes of keeping track, but what about folks who come to depend on your module? and your sharedir h2xs-1.0.0 set of templates ... which included the controversial Fuzzy.PL and the obsolete Fnork.PL , both of which are gone in Module-Cooker-0.02 .... but Module-Cooker-Fantastic-0.01 depends on both files and doesn't include a copy.... or some such fantasy scenario :) :D Your template sets probably won't change that drastically ...	[reply]