# from Christopher J. Madsen
# on Thursday 28 February 2008 23:34:
>Module::Build::Dist:
> Making the trivial changes outside of version control
> that I've described here (VERSION sections & README)
Ok, but why is that not also a separate developer tool?
Note: one trouble with the "eval {require My::Build::Class}" is that if
you have create_makefile_pl set to passthru, you get a compatibility
Makefile.PL which (unconditionally) wants My::Build::Class (which is
okay if you don't mind 99% of cpantesters sending you FAIL reports.)
>Release framework:
> Checking version control status
> Running tests
> Building tarball
> Uploading
Don't forget to test the pod, podcoverage, kwalitee, disttest, checking
the MANIFEST, and checking the Changes file for a new entry.
Perhaps I need to document this a bit more and turn it on itself...
http://scratchcomputing.com/svn/CPDK/trunk
--Eric
--
Turns out the optimal technique is to put it in reverse and gun it.
--Steven Squyres (on challenges in interplanetary robot navigation)
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
