Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • As my systems have gotten larger, I've found the best thing to do is to have ALL of the modules with the same version number.

    That way if you use recursive tree loaders or what have you, you can scan through the tree (in a test script) to make sure you don't have any old files left over from a previously installed version that are still getting loaded despite the class name changes you made at version $foo.

    So what you need then, would be something that could read the Perl files [cpan.org], find all the version strings [cpan.org], and then change them [cpan.org] to match the version in the main module of the dist.

    Or hell, set it to auto-increment from whatever the current version it finds in the version string of the base module...

    Link that into your module release process, and then the version incrementing is automated for you.

    Implementation is left as an exercise for the reader (but shouldn't be too hard, and a good exercise to learn to use a Perl document parser [cpan.org]).