Use of 'revision number' in RPM or DPKG (or other) packaging numbering..

[Michael March <mm...@gmail.com>]

Is anyone using or embedding the revision number from Subversion when whey
create package of their software (like using RPM or DPKG)?

For instance.. program-name.[major version].[minor version].[subversion
revision number]

I seen a few post and blog entries on it here and there.. but no definitive
arguments for or against.

thanks!

-- 
<admiral>

Michael F. March -

Re: Use of 'revision number' in RPM or DPKG (or other) packaging numbering..

[Michael March <mm...@gmail.com>]

Ugh.. I was thinking the same things as the points you brought up.. For
instance.. I have 'combined' repositories and thus the rev numbers
changed... it was a mess..

However.. I read in a lot of places were people use the rev plus path as a
TAG..  I believe I even saw that in some official Subversion docs..

I guess if you KNOW you'll never combine repos... then this might be an OK
idea.



> On Jun 17, 2007, at 23:16, Michael March wrote:
>
> > Is anyone using or embedding the revision number from Subversion
> > when whey create package of their software (like using RPM or DPKG)?
> >
> > For instance.. program-name.[major version].[minor version].
> > [subversion revision number]
> >
> > I seen a few post and blog entries on it here and there.. but no
> > definitive arguments for or against.
>
> The argument against is that you shouldn't assign any special meaning
> to the revision number, beyond what it actually is: the number of
> changes that have been made in the repository:
>
> http://subversion.tigris.org/faq.html#globalrev
>
> Specifically I'm thinking that the revision number could change, if
> you combine your repository with another, or split your repository.
>
> However, there are those who have seem to have decided to embed the
> revision number in their version numbers. The Opera web browser, for
> example: I have version 9.21.3678 installed, where 3678 appears to be
> some kind of revision number.
>
>


-- 
<admiral>

Michael F. March ----- mmarch@gmail.com
Ph: (415)462-1910 ---- Fax: (602)296-0400
P.O. Box 2254 ---- Phoenix, AZ 85002-2254
          "Seriously" - HSR

Re: Use of 'revision number' in RPM or DPKG (or other) packaging numbering..

[Ryan Schmidt <su...@ryandesign.com>]

On Jun 17, 2007, at 23:16, Michael March wrote:

> Is anyone using or embedding the revision number from Subversion  
> when whey create package of their software (like using RPM or DPKG)?
>
> For instance.. program-name.[major version].[minor version]. 
> [subversion revision number]
>
> I seen a few post and blog entries on it here and there.. but no  
> definitive arguments for or against.

The argument against is that you shouldn't assign any special meaning  
to the revision number, beyond what it actually is: the number of  
changes that have been made in the repository:

http://subversion.tigris.org/faq.html#globalrev

Specifically I'm thinking that the revision number could change, if  
you combine your repository with another, or split your repository.

However, there are those who have seem to have decided to embed the  
revision number in their version numbers. The Opera web browser, for  
example: I have version 9.21.3678 installed, where 3678 appears to be  
some kind of revision number.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org