-----BEGIN PGP SIGNED MESSAGE-----
I was thinking about something exactly like this too. For example I have
spotify installed in /usr/local in one of my AppVMs and would really
like to have .desktop file for it created automatically (currently I use
qvm-run manually, even though I could create .desktop manually).
I think the way to go is:
1. Have apps.templates and apps.tempicons (icon templates) directories
in every VM (/var/lib/qubes/*/*), not only templates. For templates sync
them from /usr/share/applications, for non-templates sync them from
2. While creating (or listing for Qubes Manager) .desktop files, first
look into AppVMs own apps.templates, then fallback to the one from VM
template. Same for apps.tempicons.
3. In any case, create .desktop files in apps directory of the VM
Unanswered question: how to deal with /usr/local/share/applications in
the template itself? According to the above algorithm, it will be
ignored. I don't see any use case for template-only application
(installed into /usr/local there). But surely somebody will trip over it,
sooner or later.
Am I missing anything else?
BTW Here is the code for Qubes 4.0:
Especially interesting function: appmenus_create.
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----