Magnus Therning schrieb: >>Our release structure isn't like that at all. We just take a snapshot >>of the state of current and that's a release. The rolling part means >>that the difference between releases is all the updates we've done. >> >>A release is out of date seconds after it's been made. We don't touch >>it after that. > > > How does Arch cope with big changes that affect a large set of the > available packages?
Look at what happened with gcc4 migration and libtool-slay recently: The new packages went to [testing] until the migration was (almost) finished, then the new versions were moved from [testing] to [current]/[extra] when everything seemed stable. That was a 500MB Update for many people :) Unfortunately, [current] and [extra] didn't see many updates during the testing period, so many packages there were out of date. _______________________________________________ arch mailing list arch@archlinux.org http://www.archlinux.org/mailman/listinfo/arch
