El 15/10/11 15:13, Kern Sibbald escribió:
> [snip]
>>> For example, my personal package for 5.2.0rc1 is bacula-5.2.0-0.1.rc1.fc14.
>>> 0.1.rc1.fc14 is the release tag. The 5.2.0 stable release will have a 1.fc4
>>> tag which is greater than 0.1.rc1.fc4.
>>>
>> Ok that could work too for us.
>>
>>> Any debian/ubuntu packager guru here ?
>>>
No guru here, but at least I know my way around ;)
In debian and derivatives, this would be:
5.2.0~rc1 < 5.2.0~rc2 < 5.2.0 < 5.2.1
... for upstream releases
(the point being '~' sorts before anything else for this purpose)
hence, the full version string (including packaging revisions) would be:
5.2.0~rc1-1 ... < 5.2.0~rc1-4 ... < 5.2.0~rc2-1 ... <
< 5.2.0-1 (first packaging release for 'stable' upstream 5.2.0)
and so there is no need to invent releases like 5.2.0-1final-2 or
the like.
and then even, 5.2.0+git20111009-1 for patches applied after 5.2.0 but
not part of 5.2.1 (or backported)
which sorts after 5.2.0-whatever but before 5.2.1
hope that helps
J.L.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
