>>>>> "CL" == Chris Lumens <clumens@xxxxxxxxxx> writes: CL> Making a new anaconda means making new first and second stage CL> images, which means making new CD and DVD images, which means a CL> huge headache for mirrors and for keeping track of all these CL> versions of images floating around. The thing is, if you're spinning your own distro then you should be able to figure out how to rebuild the anaconda RPM out of current CVS. The last time I had to do it it took only a few additional minutes to build an anaconda with fixes, along with other packages (kudzu in this case) that needed updates. The problems crop up when the current development version becomes unsuitable for installing a current tree (as happened with the switch to yum). At that point it might be nice if the anaconda developers would consider checking any critical fixes into the release branch for those of us who regularly respin our distros, but I don't see the point in actually doing releases. - J< -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
