On Thu, Nov 17, 2005 at 02:02:09PM -0500, Jason Chu wrote: >On Thu, Nov 17, 2005 at 09:56:47AM -0800, Doug Jolley wrote: >> >> Well, I've been playing with Arch Linux for about 2 months now and I >> certainly like what I'm seeing. For my own workstation, it's great. >> However, I'm now thinking about moving on and actually using Arch in >> some production installations. In that regard, I have some questions >> about how the rolling release system works. >> Hypothetically, let's say that the latest released version is 'Yawn' >> and the next version to be released is 'BleedingEdge'. So, put >> differently, BleedingEdge is currently under development and >> development work has been completed on Yawn. As the development work >> is proceeding on BleedingEdge, does Yawn receive security updates and >> bug fixes? If so, how long does this policy of providing security >> updates and bug fixes to Yawn continue? >> Thanks for any input. >> ... doug > >I know lots of other people will jump on this, but I wanted to as >well... > >What you've described is more of a frozen release system. Multiple >branches moving forward at the same time. > >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? I still remember trying to use Debian Unstable at the time they switched from libc5 to libc6. It was so painful I couldn't take it and spent 2 years running Mandrake. Recently the changes to GCC's C++ ABI has prompted big changes and from the sidelines it looks like the work required (in Debian) is quite involved. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) [EMAIL PROTECTED] http://therning.org/magnus Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works. The NSA response was, "Well, that was interesting, but there aren't any ciphers like that." -- Gus Simmons, "The History of Subliminal Channels"
pgp4UkDXi5sSN.pgp
Description: PGP signature
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
