Jonathan Dieter wrote:
Okay, I'm going to answer what I *think* you're asking, but I'm not
sure. In your scenario (which is what I'm using on the test server),
createprestorepo.py would create all three drpms (though some thought
needs to go into how we're going to trim them in the future).
As for making the drpms for core => updates, I took the lazy way out. I
just mirrored core and updates all into the same local directory on the
test server. Then, createprestorepo was able to find all the update
paths.
This is exactly what I asked :o)
Just needed to understand how that was supposed to work.
Sure we need to think about a good way to solve this, but for now, I
just needed to understand how that was supposed to work.
Thanks.
/Thomas
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
