Procedure for verbatim takeover from FN to FN+1?

[Paul Howarth]

Jesse Keating wrote:
> On Sun, 22 Jul 2007 17:39:59 +0200
> Axel Thimm <Axel.Thimm at ATrpms.net> wrote:
> 
>> Inherit a package from FC6 into F7 (and later) w/o having to rebuild
>> it, e.g. no waste of dist/mirror space for large data-only packages. I
>> know it has been done before for a couple of packages (texmf trees for
>> example?). Anything that is a firmware or pure data
>> (e.g. dist-agnostic) is a candidate for this, but currently being a
>> manual procedure it is only worth while for bulkier bits.
> 
> A) You must not have any build of that package tagged for later
> collections.
> 
> B) Build in the earliest collection still active
> 
> C) Once pushed as a stable update, future collections will inherit the
> build, provided no other build has been tagged in the future
> collections.
> 
> Using 'list-tag-inheritance' should shed some light on this:
> 
> $ koji list-tag-inheritance dist-f8
> dist-f8 (12)
>   └─dist-fc7-updates (14)
>      └─dist-fc7 (5)
>         ├─fe7-merge (11)
>         └─dist-fc6-updates (2)
>            └─dist-fc6 (1)

So supposing a package is buildt for dist-fc6-updates and nowhere else. 
The current state of play is that it "appears" in the repos for all 
subsequent releases, which is good. But what happens when FC^ is EOL-ed? 
Will it then be necessary to build the package for one of the later 
tags, somewhat defeating the object of the exercise?

Paul.