On Tue, 10 Sep 2013, Michael Schroeder wrote:
On Tue, Sep 10, 2013 at 04:05:34PM +0200, Frederic Crozat wrote:
Le mardi 10 septembre 2013 ? 16:02 +0200, Jan Engelhardt a ?crit :
On Tuesday 2013-09-10 15:28, Frederic Crozat wrote:
One extra issue is to ensure upgradeability of whatever existing scheme is in use to the new scheme. rpm epoch anyone? ;)
I've been relucant to change gcc from using gcc48-4.8.1_20130909 to gcc48-4.8.1_202388 for that reason. Unfortunately gcc48-4.8.1_20130909 is not upgradeable to gcc48-4.8.1_svn202388 so I have to wait for GCCs svn revision to increase beyond 20130909 ;) Or use a different separator (+ and . match _ but - would be newer).
Don't we have '~' separator in RPM to support this kind of versioning now ?
Yes, but not applicable in this case. Remember the sort order:
4.8.1~s < 4.8.1 < 4.8.1_s < 4.8.1_2
Hmm, usually, I tend to use git checkout (or any other vcs checkout) before a particular release is out, so 4.8.1~s is ok.
But now, I understand it doesn't handle all the options :(
You just have to wait until 4.8.2 if you want to introduce a new numbering scheme ;)
Or completely alternative to this whole scheme just package a diff alongside a released tarball. Bonus: you get the possibility of being able to verify its contents with an available signature. Bonus 2: less load on the source server(?) Bonus 3: easier to see what the changes since a release are. Oh, and then provide incremental diffs whenever you update the package rather than exchanging the diff. Richard. -- Richard Biener <rguenther@suse.de> SUSE / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 GF: Jeff Hawn, Jennifer Guild, Felix Imend -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org