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)
Will be available to all qubes based on the template. 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](TODO.
[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
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]
Will only be available in the app qube where you installed it.
> ⚠️ Updates are simple but manual (one click for qube apps and one-command for snap packages.
When the software is available as a "snap package" (search availability here) Read more at Installing Snap Packages (official documentation)
When the software is available as a "flatpack package" (search availability here). Qube Apps - developed by Micah Lee, a trusted community member.
Standalone qubes are dedicated qube. You can't create templates based on them.
> When do I need this?
> Here you'll install a .deb or .rpm for download and you only want to use this software in a single qube.
⚠️ Updates are manual and tiresome. It's basically repeating the whole install process! (bad security practice)
See how to do this here: https://forum.qubes-os.org/t/2890/1