Is it clear what the preferred approach is for using programs that aren’t available via Flatpak or Snap? For me, that would be megasync, for example. I’ve read that systemd-sysext is supposed to be used, but is that more for developers or also for users? I also read a comment that someone used Distrobox and Podman. What is the recommended approach for users?
At this point in time, the answer is basically “wait for it to be made available on Flathub or the Snap store” or “figure out how to install it somewhere in your home directory yourself.”
1 Like
I tend to use AppImages or self-contained apps from compressed files found on the download pages.
1 Like
Yes, I see one shouldn’t try to ride the horse while it is still in the box, and even though it’s probably too early for a feature request, I hope there will be a corresponding option later, as I think some of us have these one or two deal-breaker apps that aren’t (yet) available through these channels. But I like the path taken for KDE Linux, I use a similar approach to my daily driver, a fairly unmodified Debian, mainly with flatpaks and very few native apps and snaps.
By the way, from a user perspective, I think BlendOS’s solution for container and third-party app handling is great. Straight forward and can be used via both GUI and CLI - really simple and nice, if you’re ever considering something like that.
Anyway, thank you very much and have a nice Sunday everyone!
If you are interested in diving into details, quite a bit of discussion among KDE Linux contributors has occurred here: Document supported/recommended methods for enthusiasts and developers to extend the system (#12) · Issues · KDE Linux / KDE Linux · GitLab
1 Like
Yeah, thank you, that makes it pretty clear that Nate has already an eye on it. I’m always amazed by what this guy can all do. It seems like his day has more hours than mine. It’s great to have him.
1 Like