Re^3: "Subversion" revision numbers as 0.01

Having a common version for all the files on the repository can also be an advantage. For instance, on multifile packages, you don't have to worry about incrementing the version number on the main file every time you change any other one.

The only real issue is getting used to non consecutive version numbers.

Comment on Re^3: "Subversion" revision numbers as 0.01_blah

Replies are listed 'Best First'.
Re^4: "Subversion" revision numbers as 0.01_blah by adrianh (Chancellor) on Jun 05, 2005 at 12:04 UTC
Having a common version for all the files on the repository can also be an advantage. For instance, on multifile packages, you don't have to worry about incrementing the version number on the main file every time you change any other one. Maybe. If you only ever have one package in your repository, and you don't mind your version numbers getting incremented by tags and branches. To me the repository version and the module versions are completely different concepts and keeping them separate is the easiest solution.	[reply]

Replies are listed 'Best First'.

Re^4: "Subversion" revision numbers as 0.01_blah
by adrianh (Chancellor) on Jun 05, 2005 at 12:04 UTC

Having a common version for all the files on the repository can also be an advantage. For instance, on multifile packages, you don't have to worry about incrementing the version number on the main file every time you change any other one.

Maybe. If you only ever have one package in your repository, and you don't mind your version numbers getting incremented by tags and branches.

To me the repository version and the module versions are completely different concepts and keeping them separate is the easiest solution.

[reply]