100% agree with you OP.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
To still sorta replicate that, I just set up a script at /usr/local/bin/update
for it:
#!/usr/bin/env bash
sudo emaint sync -a &&
sudo emerge -utDU @world &&
sudo emerge -c;
flatpak --user update;
doom upgrade &&
doom sync &&
doom purge
I use very minimal software and usually don't care about Flatpak
I use fedora as well and I just update through the GUI. It's more stable that way and waiting until I turn off my computer for them to apply is not a big deal.
I'm using MX Linux and don't use any flatpak or snaps, only good old debs
I use one command to upgrade the whole system: paru
one one system and yay
on the other laptop.
Fedora updates flatpaks automatically, system updates too, but you need to reboot. Which Fedora version do you use?
flatpaks are all updated at once, just like distro packages, so yeah you might need to commands, but that's still very different to having each application update itself (and the security hell implied by that)
Also I think pkcon can manage your updates across various backends (unless you are on Arch, where I think there are both technical & ideological objections to having a simple tool that just works)
I know that a lot of people share the same thoughts with you but I respectfully disagree. If you want your system to be updated only with your apt/yum/dnf program, then just don't install anything useing snap/flatpak/etc. Sure, you will not have all the apps available in the repos, which was also the case in the past before these systems. Back then, your only option was to compile from source, which was more work-intensive than flatpaks/appimages/snaps. And updating was also much more complicated. Therefore, unless you wanted something really special, you'd stick to your repos. Flatpaks allow developers to distribute their software (and users to install it) in a less labour-intensive manner for the developer. Compiling and testing your app for Debian, Fedora, Arch, SuSE, MX-Linux, Linux Mint, Linux Mint DE, Gentoo, and all the other popular distros is an impossible task for small developers. Flatpaks was a godsend for them and for the users who don't want to compile from source. Now, you can argue that we shouldn't have all these systems (flatpak, snap, appimage, docker, etc...) but one would be OK. And again I will disagree. One of the most important aspects of FOSS is diversity. Embrace it even with its drawbacks. It would require a much longer post to explain this and others have done it already better than I would.
The official software manager on my Fedora system (Discover) presents me with Flatpaks. If I use Discover for updating ,the Flatpaks will update too. But when I use the official CLI tool to upgrade the system only RPM packages are updated. The other package managers on the system are not affected (Flatpaks, Snap, Cargo, PIP). I think there should be no discrepancy between CLI and GUI interfaces for system updates. The fact that I should "remember" how to update stuff shows that something is wrong or is not perfect.
I mostly stick to things in the repos, if theres something I want that's not yet packaged I package it myself because Gentoo packages are fancy bash scripts with libraries (eclasses) to handle the normal make && make install sort of things for most build systems
It's wild what can be done with some clever aliases. Linux is better now than ever before.
Perhaps a small bash script to iterate through all of the package delivery mechanisms' for updating everything?
Snap forces updates, and you cannot disable them. So if you use snaps, I guess you can stop worrying and keep going with your usual apt routine.
What about pkcon? I haven't used it in particular, but packagekit based GUIs work pretty well in my experience, and then it supports flatpak/snap/apt/kde addons/etc in one interface, which is better than it was originally.
Nah, I don't miss them really, flatpaks are much more convenient and for me fedora kinda just updates itself automatically.
Also, pretty much all graphical app stores on linux support flatpaks and the distro's default package manager, so you can update everything from there...