
Op woensdag 28 december 2016 15:00:19 CET schreef nicholas:
i am well aware of the commands. Users new to tumbleweed are NOT. The information that is supplied is not clear. You can see this from forum posts. (including one of the replies to this thread) yes "zypper dup ---no-allow-vendor-change" should be the *one and only one* *default* and *communicated* method of updating tumbleweed (unless the user has an explicit need otherwise) then we do not need all the [epic poems regarding ifs, buts, mights, shoulds]. Since the command is quite long lets create a shortcut of some sort and include in TW. *Then communicate clearly*.
I agree here, 100 %. Love the plan. For no other than reasons of logic. We cannot know what a user may add repo-wise. We even offer a "Plain RPM folder" as an option to add repositories. So, whatever's in there, the user will no want to be replaced by some version that ( suddenly ) appears in some other repo and break from the local repo. My rule for TW users: 'zypper dup --no- allow-vendor-change' is always OK, 'zypper dup' most of the time. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org