Does anyone know how I could ascertain the rationale for this upstream configuration diversion?
I ask here instead of immediately filing an issue about my greviances because Why doesn't discover-notifier enable offline updates by default if they're recommended? - #14 by ngraham - Help - Discuss states
Many here do not use that notifier (or even have it removed).
They prefer the native openSUSE tools like YaST > Software and zypper. So I guess interest in this phenomena will not be that great.
Thanks, that’s no problem. I’m only interested in attracting interest from the maintainers anyway, which can only be so many people.
There are (almost) no maintainers here. this is a user to user forum.
If you have reasonable arguments why it should be enabled by default beyond “Oh! But it is s-o-o-o-o c-o-o-o-l!”, by all means, submit bug report. Or even better, branch, modify and send request to merge you changes.
@rokejulianlockhart
Please note that people do not really like it when a default changes. They probably use the default as such for years and when a default changes they will be the victim of unwanted actions!
That’s the point of this post, @hcvv. Why diverge from upstream?
@arvidjaar, I have no idea what that means.
For me the default is what openSUSE delivers me already for years. Not what is happening in other distros or what happens upstream.
You do not quite seem to understand this. But when people run their system since years to satisfaction and they have it configured there where they thought they wanted to deviate from the default (the one that is there on installation, not the one in far remote upstream), it will hit them heavy when a configuration value changes from one moment to the other because the default they use (often without knowing) has changed.
The only thing one could do to avoid damage done by changing defaults is by always configuring every parameter that exists and never trust on defaults. I would not like such an environment.
There’s nothing for me to not understand - I simply disagree, as the upstream developers do.
The Plasma developers only have a view on their desktop environment. But openSUSE/SUSE has a view on a complete set off different distributions. The Plasma updater does not fit the needs of all distributions. Thats why openSUSE decided to use specialized built in tools and mechanisms to keep the distro up to date. There is no need for a 3rd party DE updater from the Plasma team when tools for distribution updates/upgrades exist…
That’s not what Why does `plasma-notifier` not enable "Use offline updates" by default? discusses, @hui. That’s a separate topic.
This is the exact topic what is discussed here. The plasma-notifier and Discover are no qualified tools to update Tumbleweed (or any other distribution which has its own updater tools). Thats why some additional features are disabled because they meddle with proper distribution update/upgrade management.
@rokejulianlockhart Can you explain where it either enables/disables this feature in the openSUSE build process?
https://build.opensuse.org/package/show/KDE:Frameworks5/discover
I see in various places about offline updates discover-5.27.7> fgrep -r "Offline" * | less which is tied in with PackageKit, but to me it looks like it’s upstream whom disable (But I’m probably wrong?)
libdiscover/backends/PackageKitBackend/PackageKitUpdater.h: bool m_useOfflineUpdates = false;
You need to understand that openSUSE is a do-ocrity, if you have an itch for something as already pointed out, submit your fix to the package. If it’s a really a bug (If you started a bug report to one of my packages with “I have a grievance…”, I would most certainly close as "Won’t Fix) report it https://en.opensuse.org/openSUSE:Submitting_bug_reports
How do offline updates do so? That’s nonsensical.
@rokejulianlockhart so you just blindly accept updates? Do you check what is updating and why…
Are they actual changes or some dependencies that caused a rebuild (hint, look at the version numbering)…
I don’t know what you refer to.
@rokejulianlockhart The updates that arrive in each snapshot, as in the list that appears in the Mailing List post?
You find an explanation why offline updates are disabled by default here:
Use a german to english translator like www.deepl.com
Offline updates means “system update mode”. I recommend the usage of “system update mode” provided by systemd:
# man systemd.offline-updates
Use OpenSUSE Leap, update your machines with self made systemd services and shell scripts in system update mode. Deliver all software packages (rpm) from our own packet repository. Build your own packet repository (YUM repository). Howto:
Work with patches (zypper lp and patch-info) and forget OpenSUSE Tumbleweed.
I don’t want to. I’m going to stick with Tumbleweed. Thanks for the explanation about how to do so if I were to use Leap, though.
@GrandDixence2, I’m really confused about this point. You seem to recommend using offline updates, as does the post you linked. How does that demonstrate why it is not the default…?
Indeed, I’ve not ever read the mailing list. I never expected that to update a computer I’d have to.