On Thu, 2015-01-22 at 13:00 -0500, S. wrote:
Hope that explains the thing a bit.
Wow, very cool process. Thanks for the great explanation. I personally prefer a cautiously stable rolling system with minimal breakage, so it sounds like a good balanced approach.
Glad that we provide what seems to be the right thing for you.
This reminds me of another question: On a recent fresh install of Tumbleweed, I noticed there is an openSUSE-Factory-Update repo (http://download.opensuse.org/update/factory/) and also an openSUSE-Factory-Oss (http://download.opensuse.org/factory/repo/oss). I can't remember if I added the openSUSE-Factory-Oss repo or if it was enabled by default, but I do know that the openSUSE-Factory-Update repo was enabled by default. First, shouldn't those repos now be called "Tumbleweed" instead of "Factory"? And additional, if this is a rolling branch, why would there be a regular release repo and also an "update" repo? Isn't the http://download.opensuse.org/factory/repo/oss repo always up-to-date with the latest rolling release packages? Isn't an "update" repo on top of that redundant?
ok, that's two answer... the name is reported in
https://bugzilla.opensuse.org/show_bug.cgi?id=913561 and is basically a
remaining for the not that old fact that Factory was 'renamed' to the
outside to be called Tumbleweed (which was a slight different approach
before).
The /update channel is actually there to 'never be used'. It's a channel
'of last resort' in the unlikely case that we have some breakage in the
Factory repositories, which makes it impossible to publish, yet we have
a security update that we want to distribute to users in a much shorter
time. in THIS constellation we would publish the security update in the
update channel. Once Factory can be published again, the update channel
would be cleaned out as well.
Cheers,
--
Dimstar / Dominique Leuenberger