I use Linux Mint on my work computer, and I keep getting slowed down whenever I need software that isn't available in the built-in software manager. For example, I've had to research whether tools such as Podman, cosign, or BlueBuild should be installed with apt, curl, a .deb package, an AppImage, or some other format. On Windows, I'm used to downloading an .exe or .msi from the developer's website and running an installer. I'd rather stay on Linux, but these repeated installation decisions are becoming frustrating. How do other people handle this, and is there a good general approach I can learn?
3 Answers
Linux software usually comes through a package manager rather than a standalone installer. Mint is based on Debian and Ubuntu, so instructions for those systems are often relevant, but check that the version and repository are compatible. For tools that aren’t in the default repositories, use the project’s own documentation and prefer official repositories or signed packages. Flatpak can also simplify desktop applications, while developer tools may intentionally be distributed through their own repositories or container-based setup.
You don’t necessarily need to use the terminal for everything. Mint’s package tools can handle many applications, and a downloaded .deb file can often be opened and installed graphically. For something like Podman or specialized development tools, though, the official instructions are usually the safest path because they may require a newer package version or an additional repository. The main skill is learning to identify the software’s intended distribution method rather than expecting every program to use the same format.
A lot of this becomes routine after a while. First check the Mint repositories and Flatpak, then look at the project’s official installation documentation. Depending on the project, you may use apt, install a trusted .deb, or use an AppImage or container image. Keep a small notes file with the commands that worked for you; after a few installations, you’ll recognize the common patterns. Just avoid blindly running commands copied from random websites, especially anything involving sudo or downloading and executing a script.
That’s the part I’m still getting used to—some projects provide a package, while others expect you to add a repository or run a setup command. Keeping notes and checking the official documentation should make it less repetitive.