[Openvas-devel] Planning OpenVAS 4 Beta

Stephan Kleine bitdealer at gmail.com
Wed Nov 10 00:49:13 CET 2010


On Wednesday November 10 2010 00:18:14 Jan-Oliver Wagner wrote:
> On Monday 08 November 2010 15:45:28 Stephan Kleine wrote:
> > On Monday November 8 2010 12:06:21 Jan-Oliver Wagner wrote:
> > > How to apply version number for OpenVAS
> > > ---------------------------------------
> > > 
> > >  * Any stable release should be given a version number N.N.N.
> > >  
> > >    Thus source code tarballs are named "module-name-N.N.N.tar.gz"
> > >  
> > >  * Any Beta and RC release refers to a next major release, never
> > >  
> > >    a minor release. Thus versions like "N.N-beta1" or "N.N-rc1"
> > >    are applicable, but not "N.N.N-rc1".
> > >    This ensures, that for example 2.0.0 is greater than 2.0-beta1
> > >    when applying simple version comparison.
> > 
> > Which doesn't work cause rpm doesn't allow "-" in the version string so
> > one had to use 2.0.beta1 which is "bigger" than 2.0.0.
> 
> alas, this is not getting an easy task ;-)
> 
> How about "N.N+rc1"?
> At least 2.0+rc1 is less than 2.0.0.
> Do we get trouble with some packaging rules with "+"?

Good idea, + seems to work nicely as long as the final version is x.0.0 and 
the betas & releases only x.0.


More information about the Openvas-devel mailing list