On Dec 8, 2008, at 4:23 PM, Chris Lumens wrote:
(4b) We'll need to store the corresponding sources along with the
updates images.
Considering most of the changes would be to python files, shouldn't
that
cover us? If we also commit the changes to the release branch in
anaconda's git repo, does that cover us the rest of the way too?
You have to distribute in the same way that people get them. The git
repo becomes fuzzy as to whether or not it satisfies. Given that
there could conceivably be, eg, isys changes, it probably behooves us
to just always build a new package and push it into the -updates
repository if we're going to go this route. But doing so raises the
pricklies for me of managing and doing updates while still juggling
all of the other things that have to be done for the next release.
Jeremy
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
