That Template thing is potentially a tricky bit. Flexability, and the ability to switch on demand, based on the users need(s). I think should be addressed. To my knowledge, there really isn't anything that currently addresses this as effectively, as it could. This option, if done correctly, could possibly set it apart from the others already available.

Then there's the versioning strategy. Based on what? Everyone has their preferred strategy. While some, may choose none -- if only for a "one off".

Just some thought's that come to mind.

--Chris

#!/usr/bin/perl -Tw
use Perl::Always or die;
my $perl_version = (5.12.5);
print $perl_version;

I think I'm just going to ignore the versioning issue so far as trying to create default "ignore" files. Module::Starter has options to do this, but I think it is easier for the user to just create a local profile dir and add whatever files she thinks are needed. The standard M::C templates will be pulled in if they are not in the local dir (assuming the profile name exists in the standard distro) so it should be trivial to add one's favorite versioning config files or LICENSE or whatever without having to deal with every file in the standard distro profile.

M::C will then generate the MANIFEST file (via MakeMaker) once all files have been generated. And of course, one could have a custom MANIFEST.SKIP in the local profile dir, as well. I can easily see a normal use-case where the local default profile dir would only have a couple of files in it, with everything else coming from the standard distro default profile.

It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.