Re: "Subversion" revision numbers as 0.01

I'd be very wary of using the SVN repository revision as your package's version number. You're conflating a particular state of your repository with a particular public release. Not as automagic, but it might be better to manually retain a more traditional major.minor.patch variable and use svn cp to create a tag in your repository.

Update: Again, this is IMHO. I haven't maintained anything publicly released with SVN (haven't moved my piddling couple of CPAN modules over to SVN yet), so don't take this as gospel. I'd be interested in hearing more from people who are using SVN in live practice.

--
We're looking for people in ATL

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

Replies are listed 'Best First'.
Re^2: "Subversion" revision numbers as 0.01_blah by adrianh (Chancellor) on Jun 05, 2005 at 00:50 UTC
I'd be very wary of using the SVN repository revision as your package's version number. You're conflating a particular state of your repository with a particular public release. Agree completely. For a start it completely falls down if you maintain more than one module in the repository. Subversion has repository based version numbers so any commit to the repository is going to increment the version number, whether it has anything to do with the module or not.	[reply]
Re^3: "Subversion" revision numbers as 0.01_blah by Fletch (Bishop) on Jun 05, 2005 at 01:12 UTC
For a start it completely falls down if you maintain more than one module in the repository. Yup, to say nothing of revision bumps created on branches or by creating tags. -- We're looking for people in ATL	[reply]
Re^3: "Subversion" revision numbers as 0.01_blah by salva (Canon) on Jun 05, 2005 at 01:39 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. The only real issue is getting used to non consecutive version numbers.	[reply]
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]