>> Before I get started explaining this, I'd like everyone to keep in mind >> that this should be completely separate from all the mirrors, ISO >> images, etc. This is a whole other system in order to keep bureaucracy >> and complexity to a minimum. > > > Why? Why not make it a subdirectory of the 'updates' path to handle these > images, if they are released. Then every mirror can have them, you can > use the same mirror you're using for everything else in the install and > we don't have to worry about a single site being down and no one getting > important anaconda updates to perform their install? It's my understanding that we do not want to modify the trees on mirrors after the release, as the tree would now be different from the corresponding ISO images. Am I incorrect about this? - Chris _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
