On Saturday, June 22, 2013 12:01 AM, Clint Savage wrote:
> Mathieu,
>
> The reason is that gl6.0-updates packages will be tagged after they are
> built into gl6.0-updates-candidates and tested.
But that's the same thing for gl6.{1,2}-updates: packages there will be
tagged after they are built into gl6.{1,2}-updates-candidates and tested.
> In this way, we can have
> updates separate with inheritance for the generic updates repo.
> Essentially, everything is built and tested in the left tags and is moved
> to the appropriate -updates tag as it's approved. Then we can mash the
> updates repos together and keep the iso repos (gl6.x) separate.
It seems you're explaining the need for two sets of tags: gl6.{1,2} and
gl6.{1,2}-updates.
Indeed, this separation is what allows making an ISO from gl6.{1,2}
while publishing updates in gl6.{1,2}-updates.
But that wasn't my question. :)
Let me reformulate:
* gl6.0-updates **does not** inherit from gl6.0
* gl6.1-updates **does** inherit from gl6.1
* gl6.2-updates **does** inherit from gl6.2
My question was: why the differences in inheritance schemes?
( I'm sure I'm simply missing something obvious here, but I can't figure
out what ^_^ )
--
Mathieu