On Fri, 2007-03-23 at 14:50 -0500, Jason L Tibbitts III wrote:
> >>>>> "TC" == Tom \"spot\" Callaway <Tom> writes:
>
> TC> I have added a draft for handling Post Release packages.
>
> It might be worth mentioning what to do when upstream ODs on the
> crackrock and unexpectedly changes to a non-ordered versioning scheme
> in the middle of a sequence. Something like:
>
> openssl-0.9.6g
> openssl-0.9.6h
> openssl-0.9.6final
>
> Epoch is probably the only way out here unless we allow something
> nasty.
Note that this particular example would be very cracktastic as we're
talking about postrelease tags.. so presumably upstream has already
released openssl-0.9.6.
Which is not to say that upstream's twisted numbering scheme won't do
*something* unexpected. Which is one reason I'd rather see us use the
%{X}.%{alphatag} syntax always. The other reason is that using it
always makes things less complicated. Instead of asking::
Is this a prerelease or a postrelease?
If postrelease, is upstream likely to use sane numbering?
If no, use postrelease scheme
If yes, use upstreams version until they screw up one time
If prerelease, use prerelease scheme
Our rule would be::
Does upstreams version have an alpha tag?
If yes, use alphatag versioning.
-Toshio
Attachment:
signature.asc
Description: This is a digitally signed message part
-- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
