On Sat, Feb 19, 2011 at 03:24:06AM +0100, Stephan Kleine wrote:
On Friday February 18 2011 23:13:41 todd rme wrote:
Le 04/02/2011 20:05, jdd a écrit :
Le 04/02/2011 19:57, Stefan Seyfried a écrit :
Same procedure, once 11.5 comes out: remove 11.4 repos and add 11.5 => zypper dup.
could it be possible to have a link "latest" or "current" to have the repos changed automagically?
jdd
I would like something like this as well. One of the advantages I saw for tumbleweed was to be able to just set up your repositories and never have to touch them again. I know several people who refuse to use openSUSE solely because they can't do this. So I think being able to seamlessly upgrade to what amounts to a new openSUSE version without needing to do anything more than your everyday updates would be a huge benefit for tumbleweed.
+1 - the reason that killed Tumbleweed for me was when you (Greg) announced that you plan to always base it on whatever latest released distro instead of making it a truly rolling one.
Why? How difficult is it _really_ to edit 3 files, every 8 months, changing a "3" to a "4", and then a "11.4" to a "12.0"? Heck, if it's that tough, I'll make up a script that everyone can run to do this :)
IIRC you back then said that linking packages didn't work out. Can you please elaborate a bit on this part and why since I don't really get that part? (while I'm not exactly new to OBS and how linking works there)
Ok, I decided not to do this for a number of reasons: - as mentioned later in this email thread, I don't want people to have to have a whole new repo to build against. - I want to build on the solid base of our releases, and not require the build service, and mirrors, to have to send out an entire copy of the existing 11.4 (or whatever the base is) packages to the world for no reason. - versions get out of whack, so it looks like you are "downgrading" when installing Tumbleweed. This causes confusion and has the potential to cause future updates to get out of sync without making it easy to recognize - Updates get messy, and slower. I would have to monitor the updates channel and rebuild everyone of them for Tumbleweed users, ideally the instant they show up in the Update channel, due to security updates. If we don't have a whole copy of the distro in Tumbleweed, we can rely on the great work the openSUSE security and maintenance team does with updates for bugs and security issues. - reverting back. It's simpler to revert back from Tumbleweed to the "base" distro by just disabling a single repo, instead of disabling and then enabling the original ones. This makes it easier to roll back specific packages if problems occur, and gives me a simpler way to recover from errors that happen in the Tumbleweed process (like the recent zypper and libzypp and yast2 mess that happened a few weeks ago.) So, because of all of this, I feel that Tumbleweed is best off as an "add-on" repo to the base release. Now this does not preclude the fact that it would be nice to just set up a "latest release" zypper config file to always point to the latest one so we don't have to edit it every 8 months or so. That we should be able to do on the openSUSE side fairly easily I imagine. Hope this helps explain my reasoning for all of this better. please let me know if you have any questions about this. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org