On Mon, Nov 10, 2008 at 04:43:27PM -0500, Ricardo SIGNES wrote: > * Jonas Brømsø Nielsen <[EMAIL PROTECTED]> [2008-11-10T16:15:20] > > I like to be able to release distributions without necessarily > > touching a code module, if changes are just documentation, tests or > > other files. I only update package versions when code/functionality > > changes, so developers using my module can depend on this version > > number, when examining APIs, bugs etc. > > I use perl-reversion (part of Perl-Version) or Dist::Zilla to keep the same > version on every .pm file and the dist. It's a little annoying that the > version changes on things that are unchanged, but it keeps life simple.
I do this too (with a home made make target - the master version lives in Makefile.PL) and it works well, but ... I'm starting to get annoyed by the extraneous commits into the revision control system. And so I'm considering the option of not having the version number in the file that gets checked in, but expanding it for a release. -- Paul Johnson - [EMAIL PROTECTED] http://www.pjcj.net
