> > "disttag" has nothing to do with it. Basically koji has the concept of > inheritance. When we create a new distribution tag, say dist-f8, we > configure it to inherit from the previous distro's updates, ie > dist-fc7-updates. dist-fc7-updates inherits from dist-fc7, which in > theory > inherits from dist-fc6-updates, and so on. > > If you did an update and it was pushed stable (and thus tagged for > dist-fc7-updates), then getting a listing of what's "in" dist-f8 would > show > that build, provided that no builds of said package were tagged for > dist-f8. > This is how we "bootstrap" new collections and take advantage of already > done > QA work. > > Our compose tools will ask koji for all the 'latest' packages that can be > seen > via a given tag. Inheritance is followed. How "latest" is determined is: > > Look at the tag, are there any builds of <foo> that are specifically > tagged > for dist-f8, if so, use the one that most recently got the tag. If not, > look > at priority 1 inheritance and ask the same question, go until you find a > build. So IIUTC, if I build for F-7, it will be included in the F-8 yum repos as well, if nothing with that EVR exists there already? > -- > Jesse Keating > Release Engineer: Fedora > -- > Fedora-maintainers mailing list > Fedora-maintainers@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-maintainers > -- novus ordo absurdum -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
