On 12/28/2016 09:00 AM, nicholas wrote:
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*.
well from my POV that's not merely 'as clear as mud' but sows confusion and perplexations. Does that me that if you, as I do, have other repositories to ensure latest releases of other things (kernel, tools for specific projects, fixes to specific problems) that one should run the "-dup" ONLY and SPECIFICALLY on the tubleweed repository, replying of the fact that the "--no-allow-vendor-change" means my darktable (for instance) from another repository will not be updated by this 'dup"? Or if that's not the case, then what? Please don't talk about 'locks'. The whole point of those other repositories is that I want either a different style of implementation or a different way of updating. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org