On 2016-12-28 18:32, Anton Aylward wrote:
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"?
"zypper dup --no-allow-vendor-change" tries to update every package from the same repo, so yes, it would try to keep "darktable" and would not be altered. But notice I said "tries"; some times it fails. For instance, your darktable might depend on another package that is not available, and then might be removed or replaced. But what Nicholas is asking for is simply for clear documented policy, I suppose on a wiki page explaining how to upgrade TW (specifically, TW). Not for explanations on what each method does. The problem is, there is no agreement. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)