From: Jonas Bromso Nielsen <[EMAIL PROTECTED]> > The RT raises an issue with the distribution version number not being > equal to the one in the main package version, in my case Workflow.pm > > 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. > > But as the RT states this makes it practically impossible to trace > from what distribution the package came from and the current version > of 1.32 is present in several distributions.
I would be surprised to find the main module having version 0.31 in the distribution version 1.32. I would not be surprised to find a modul with version 0.31 in distribution version 0.31.46. IMHO, if you need to release a new distro because of some docs changes or some fixes in a "submodule", do not bump up the revision, use a build number for that (or whatever you want to call it, I'm talking about distribution versions in format version.revision.build. Not sure what's the standard nomenclature.) Jenda ===== [EMAIL PROTECTED] === http://Jenda.Krynicky.cz ===== When it comes to wine, women and song, wizards are allowed to get drunk and croon as much as they like. -- Terry Pratchett in Sourcery
