On 09/10/2013 04:05 PM, 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 :(
I guess it depends on how you view it. It can either be $CURRENT_RELEASE+$FANCY_STUFF_FROM_SCM or $UPCOMMING_RELEASE~$WHATS_REALLY_IN_SCM -- Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)