[csw-maintainers] A chain of updates

[Maciej (Matchek) Bliziński]

2011/12/14 Peter FELECAN <pfelecan at opencsw.org>:
> "Maciej (Matchek) Bliziński" <maciej at opencsw.org> writes:
>
>> Here's where named releases can help.  We could require sequential
>> updates. For example, legacy→dublin would be a valid update path, and
>> so would be dublin→kiel. However, legacy→kiel would not.
>>
>> If we tracked the renames, we could identify all packages that e.g.
>> have gone 1→2 during the legacy→dublin transition, and have them go
>> 2→3 during the dublin→kiel transition.
>>
>> Thoughts?
>
> Question: does this means that I can do dublin -> ++kiel ?

You can do dublin→kiel, but you cannot upgrade from dublin to a named
release after kiel. In other words, you need to sequentially upgrade
from one named release to another, with no skipping.

A thought: pkgutil could somehow keep track of this, and stop or warn
if someone attempted to do an invalid upgrade.

> Also, this means that you need to keep all the named releases or define
> an obsolescence time for a named release.

Correct.  We'd keep them for something like 3 years, which amounts to
about 6 named releases at any given point in time.

Maciej