3 ms·
maybe it's indeed time to let the system package management(apt,rpm,etc) just manage a solid BASE system, and let Flatpak etc to manage their own application sa
by synergy20 4y ago
maybe it's indeed time to let the system package management(apt,rpm,etc) just manage a solid BASE system, and let Flatpak etc to manage their own application sandboxes on top, kind of like dockers.
Appimage is macos flavor, it never needs your sudo to install the package, which is nice.
Flatpak is a redhat flavor(kind of), it needs sudo sometimes, but OK.
Snap is a ubuntu flavor(kind of), it is like systemd that can overtake the whole system, it can install package and even the whole system I was told, too much as a package manager for me.
I don't use Snap. Appimage is not as widely adopted as the rest two? I think Flatpak is a great middle ground.
It will be really cool if KDE and Gnome work together to build this.
- johnny22 4y ago> maybe it's indeed time to let the system package management(apt,rpm,etc) just manage a solid BASE system, and let Flatpak etc to manage their own application sandboxes on top, kind of like dockers. This is kind of how immutable systems like fedora's silverblue, and suse's microos are setup. The base systems are still built with rpm, but for user packages you either use flatpak or stuff in containers via toolbox or distrobox. It's still possible to layer stuff on to the base image if necessary though.
- twblalock 4y agoIt's been time for that for a while now. Sandboxing and distro-agnostic packaging are definitely the way to go. They have some pain points but it's better to fix those than to go back to the older way of doing things.
- notepalf 4y ago> it's indeed time to let the system package management(apt,rpm,etc) just manage a solid BASE system It totally is! Why does a distro maintainer need to pack every known application into the OS and make sure it works? This kind of work does not scale.
- gjadi 4y agoLike *BSD, with base + ports.