seth vidal wrote : > > My plan would have been this: > > > > 1. bump release of every package in "devel" > > 2. make sure that every update of FC-3 and older either loses > > RPM version comparison compared with "devel" or is also imported > > into "devel" tree with a higher release number > > > > Then we would be ready for a mass-rebuild any time. > > Let's ask if anyone is bothered by you doing #1 with your script. > Anyone got a problem with that? > > We can do #2 iteratively post-mass-rebuild. I bet it will only be a > handful of items anyway. > > then on with the rebuild-foo. But what if we start using the ".fc4" release tag? Then no more mass release incrementing is required. > the only item we might want to delay a tiny bit on is gcc->gcc4. This has now happened, yeah! :-) Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora Core release 3 (Heidelberg) - Linux kernel 2.6.10-1.770_FC3 Load : 1.72 1.10 0.68
