There is plenty. Like module-names being hardcoded into tests.
FWIW: There are other modules which try to solve this issue.
like Module::Starter::AddModule
I think I will fall back to a more dynamic approach, using pseudo.t files in my test directory automating the updates whenever I run prove.
Things like updating .pod files and README by templates and updating the VERSION number. And updating the manifest and so on.
Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice
In reply to Re^2: Redesigning distribution with Module::Starter
by LanX
in thread Redesigning distribution with Module::Starter
by LanX
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |