OK, I see the problem. I will try the last attempt: What about using "6.0.pre32" for pre-versions and 6.0.0 for 'final' versions? The update should work flawlessly, shouldn't it?
Sorry for too many questions over last few emails...
Radek Černoch
--
Radomir Cernoch
E-mail, Jabber, MSN:
radomir.cernoch@gmail.com
Skype: radomir.cernoch
------- Original message ------
Subject: Re: [opensuse-contrib] New submit-request #4459 for openSUSE:Factory:Contrib/ipe
Date: Wednesday 07 January 2009 06:18:25
From: "Marek Stopka"
On Wed, Jan 7, 2009 at 1:11 AM, Radomír Černoch
wrote: Sorry for the delay of my answer, I have been occupied with other things last weeks.
I quite like the digit-only version numbering, but "ipe" has a _really_ weird release cycle. Every time a new major version is started, there is nothing but pre-versions for a couple of years. When a stable "X.0" version is released, the major version is increased immediately. This means, that most of pre-versions de-facto stable releases.
Therefore naming 6.0pre30 as 5.0.99.30 would cause a lot of confusion, because the package's major version would be lower than the program's one in 99% of the time.
I would like to ask, whether the following workaround could be accepted: The version "6.0pre30" would be encoded as: Version: 6.0 Release: pre30.0 As soon as "ipe 6.0" is released, these tags are changed to: Version: 6.0 Release: 0 I think that such an update should work well according to SUSE package conventions. Moreover a similar system is used in Fedora packages.
No, you can't use Release number for this, because Release is automatically generated by OBS and Release tag in package is replaced by that OBS tag...
If I changed the package in the described fashion, would it be accepted? No way.
Yours, Radomír Černoch
-- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org