[opensuse-packaging] rpm versions?
We have a product with versions like: 3.0.1-dev 3.0.2-rc2 3.0.2.5 (for a customer version) ...etc. As I'm packaging these as RPM's, we've been trying to do: %define major 3 %define minor 0 %define patchlevel 2 %define relnum rc2 ...but is that going to confuse rpm? That is, is relnum going to be compared numerically or as an ASCII string, or as something else? How can we ensure that dev < rc2 < 5 for relnum? Do we need to come up with a numbering scheme like "dev is 0-20, rc is 21-40, customer versions are 41-60" etc? Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On pátek 30 listopad 2007, Dan Stromberg wrote:
We have a product with versions like:
3.0.1-dev 3.0.2-rc2 3.0.2.5 (for a customer version)
...etc.
As I'm packaging these as RPM's, we've been trying to do:
%define major 3 %define minor 0 %define patchlevel 2 %define relnum rc2
...but is that going to confuse rpm? That is, is relnum going to be compared numerically or as an ASCII string, or as something else?
How can we ensure that dev < rc2 < 5 for relnum? Do we need to come up with a numbering scheme like "dev is 0-20, rc is 21-40, customer versions are 41-60" etc?
Yes, converting everything to numbers is probably the most safe way. Some project use something like 3.0.99.2 for 3.1-RC2. -- Vladimir Nadvornik --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Vladimir Nadvornik wrote:
On pátek 30 listopad 2007, Dan Stromberg wrote:
We have a product with versions like:
3.0.1-dev 3.0.2-rc2 3.0.2.5 (for a customer version)
...etc.
As I'm packaging these as RPM's, we've been trying to do:
%define major 3 %define minor 0 %define patchlevel 2 %define relnum rc2
...but is that going to confuse rpm? That is, is relnum going to be compared numerically or as an ASCII string, or as something else?
How can we ensure that dev < rc2 < 5 for relnum? Do we need to come up with a numbering scheme like "dev is 0-20, rc is 21-40, customer versions are 41-60" etc?
Yes, converting everything to numbers is probably the most safe way. Some project use something like 3.0.99.2 for 3.1-RC2.
How high can the numbers go? Is a number like 8000 safe? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fri, 30 Nov 2007, Dan Stromberg wrote:-
Vladimir Nadvornik wrote:
Yes, converting everything to numbers is probably the most safe way. Some project use something like 3.0.99.2 for 3.1-RC2.
How high can the numbers go?
Is a number like 8000 safe?
I certainly think so, especially since rpm treats the version "number"
is treat as a plain text string. For example, I've one package where the
upstream version number is a ten digit number:
davjam@davids:~> rpm -qi wtf
Name : wtf Relocations: (not relocatable)
Version : 20051104 Vendor: (none)
Release : 1.suse93 Build Date: Mon 16 Oct 2006 07:58:00 BST
Install date: Sat 03 Nov 2007 13:45:59 GMT Build Host: davids.davjam.org
Group : Amusements/Toys Source RPM: wtf-20051104-1.suse93.src.rpm
Size : 18466 License: Public domain
Signature : (none)
Packager : David Bolt
participants (3)
-
Dan Stromberg -
David Bolt -
Vladimir Nadvornik