On Sat, 17 Mar 2007 10:46:22 +0100 "Marijn Schouten (hkBst)" <[EMAIL PROTECTED]> wrote:
> One thing we could do would be to separate hierarchy from version
> naming.
This is where upstream version numbers fail to have a decent order
(like your example where later versions have lower version numbers).
It could be done for example by extending metadata to include
definitions of unnatural ordering, but I don't think it's worth the
effort. So far we deal with that on a case-by-case basis, and live
with the pain when it occurs.
> This would prevent cases like currently with rosegarden (~)1.2.4
> (~)1.4.0 4.1.0-r1 4.1.0-r2, where it really should be 4.1.0-r1
> 4.1.0-r2 (~)1.2.4 (~)1.4.0.
For example, a simple solution is to just re-number the (presumably
older) 4.* as 0.4.* and be done. That would also solve the potential
future problem when the latest release reaches 4.* again. The sequence
I would do is:
1) copy 4.1.0* to 0.4.1.0*, commit to the tree (here you could either
rig the SRC_URI to keep the old tarball names, or copy the old
tarballs again with the new revision number)
2) Alter any packages that depend on the 4.1 versions explicitly, to
depend on the 0.4.1 versions (after you're sure the new 0.4.*
versions are in the tree).
3) Remove the 4.1* versions - after a delay (a few days, a
week, whatever, depending on how often your users are likely to
update); in the changelog note that users should expect a
downgrade and it is ok to do so. As a minimum, delay until
you're sure (1) and (2) have reached the rsync mirrors.
4) Get 1.2*, 1.4* stablilised some time later in the normal way.
Actually a quick scan of the tree shows there's nothing affected by (2)
so that step can be skipped. I'd recommend still having a delay between
the copy (1) and the removals (3) - at least long enough for the copies
to propogate to the rsync mirrors before the removals happen (I'd
probably do the copy one day, check that got through ok the next day
and do the removals then). Noting the expected downgrade in the
changelog when the higher-numbers are removed is important (this is
what users will see if they do emerge -l).
--
Kevin F. Quinn
signature.asc
Description: PGP signature
