On Mon, 2008-10-06 at 15:14 -0400, Mike McLean wrote:
> would result mergerepo creating a single repo that would only
> packages from dist-f9-ga-external if they did not exist in the
> Koji-generated repo (dist-custom-build + dist-custom),
> dist-f9-updates-external, or the blacklist of blocked packages. This is
> consistent with how Koji package inheritance currently works, and I
> think is the most intuitive approach.
It is similar, but different in potentially confusing ways. External
repos do not have build structure, so we can't really have the same sort
of inheritance behavior with a combination of external repo tags and
I don't think I even saw a reply from Seth on this. Where does
mergerepo code stand now?
mergerepo has been checked into createrepo and should do what you want,
it requires HEAD of createrepo and as soon as I make a new release yum
3.2.19-6 or 3.2.20 of yum.