Your only option is universal formats like Flatpak and AppImage. I would recommend against random deb packages or compiling from source unless it's some very tiny obscure utility that will not need any updates in the foreseeable future (so something like j4-dmenu-desktop or a fetch script).
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
Flatpak is good for user things that need to be bleeding edge. If I need to work with a server that's bleeding edge, containers are the way to go.
Yeah if they want to update system packages it's where things end up in dependency hell. You want newer X, it needs newer Y, it needs newer Z and it's a a library half the packages of the system depends on and the rest of the system goes boom.
It's actually why I went to Arch, I need to hold back packages way more rarely than I want newer everything else.
Flatpaks the best way.
If it's cli, use toolbox or distrobox. You can pull in an arch image and get the stuff from AUR.
Distrobox also works with GUI applications. Toolbox, probably too
That's awesome then. I had some trouble with an electron app so i thought it's complicated.