Installing software in Qubes OS can be a daunting experience. This guide's goal is to serve as a crossroad sign to help you navigate this landscape.
(image credit: @deeplow, via public domain, original from pixabay)
A template qube is like a boilerplace for app qubes based on it. When you install a piece of software on it all qubes based on the template will also get that piece of software.
When you install it like this, you get updates via routine updates (normal way of updating).
[recommended / "easy"] When software is already available in template's package manager Just follow the official documentation or se a practical example here.
[medium] When software is available as an additional package repository only -- example https://forum.qubes-os.org/t/5221/1
[details="other methods (advanced)"] > ⚠️ This is for advanced users only. Updates are manual.
Using the updates proxy to give software management programs internet access in the template.
In case this software installs stuff in non-persistent directories you'll need to use bind-dirs those directories persist when starting an app qube based on the template.
Examples of what can be achieved with this
- pip install in template - https://forum.qubes-os.org/t/external-repositories-pip-snap-appimage-persistent-installations-in-template-appvm/561/4
[/details]
App qubes are your regular qubes (e.g. personal or work qubes). If you install like this the application will only be available in that app qube where you installed it.
> ⚠️ Updates are simple but manual (one click for qube apps and one-command for snap packages.
Read more at Installing Snap Packages (official documentation)
Qube Apps - developed by Micah Lee, a trusted community member.
[details="Other methods (advanced)"] TODO usermode dnf / deb packages. [/details]
Standalone qubes are dedicated qubes. They are good if you want to install random software that you don't trust to be installed on your main templates and only really need to use in a single qube.
It's very flexible. The only downside really is it occupies a lot of space (like regular templates) but none of the advantages of splitting that space among app qubes.
Regardless, the security isolation and flexibility may make this a way to go for very particular pieces of software.
.deb or .rpm that you download form a website. See how to do this here: https://forum.qubes-os.org/t/2890/1> ⚠️ Updates are manual and tiresome. It's basically repeating the whole install process! (bad security practice)