in reply to Best Practice for automatic version numbers?

Just because you didn't modify Foo.pm doesn't mean your version number doesn't need to change. Does your system handle that case?

If I were going to automate version numbering then I'd likely put the version number outside of Foo.pm (into a file just for the version number) and patch my "make dist" step to increment the version number in that file after the distribution is written.

I'm not tempted to automate this since doing it manually is such a tiny part of what it takes to make a release. I certainly won't be tieing some internal revision control number to the module version number, as that adds ugliness to the version number and adds an internal-to-external tie, something that often leads to complications.

- tye        

  • Comment on Re: Best Practice for automatic version numbers? (no, how)

Replies are listed 'Best First'.
Re^2: Best Practice for automatic version numbers? (no, how)
by kyle (Abbot) on Oct 06, 2007 at 03:55 UTC

    It's easy enough to force a version number to change if it needs to.

    I think you're right about the dubious value of using revision numbers as version numbers, but I'm confident these numbers aren't used for anything. I thought they might be useful at some point, but I never found that point, and the code in question isn't used by anyone else.

    So this may be my big chance to get rid of something that's not needed. Still, I'm curious, since this seems like something that ought not to require the amount of effort that it does.

    Thanks for your thoughts.