On 11.09.2012 18:38, Lars Marowsky-Bree wrote:
On 2012-09-11T11:48:39, Patrick Shanahan <paka@opensuse.org> wrote:
Providing a stable rolling release would be impressive. Is Tumbleweed not considered stable yet? I thought it was. I too. I have been using Tumbleweed since it's inception with *few* difficulties, mostly of my own making.... :^)
I really like Tumbleweed. But it is not a rolling release; it's more of a selective backport. (Which I appreciate, honestly! It's just not what's being suggested.)
This morning, zypper dup greeted me with
2172 packages to upgrade, 315 to downgrade, 660 new, 37 to reinstall, 300 to remove, 383 to change vendor, 14 to change arch. Overall download size: 2.43 GiB.
A rolling release would have fed these into the repository over the course of the last 8 months or so when they were ready and tested in smaller increments/bundles, not as one huge jump.
You know, much like "We're not going to do the 1.0/1.2/1.4/2.0/2.2/2.4/2.6 thing any more", because such major releases were not considered appropriate for todays world? ;-)
Well, if you integrate new gcc, there is no point in saying it generates much faster code unless you offer the new code in form of newly compiled binaries. So a rolling release has even more times when you have to download tons of packages. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org