On Wed, Dec 21, 2016 at 8:19 PM, Marek Marczykowski-Górecki
<[email protected]> wrote:
> 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
> /usr/local/share/applications.

And ~/.local/share/applications too?

> 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.

If by "fallback" you actually mean "also include" rather than "only
include if the first does not exist or is empty", then I agree.

> 3. In any case, create .desktop files in apps directory of the VM
> itself.
>
> 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.

The template's /usr/local is hidden by being mounted over by the
appvm's /rw/usrlocal anyway, so IMO this is not an issue to be
concerned about.

> Am I missing anything else?

~/.local/share/applications ?

I had forgotten about it initially too.

> BTW Here is the code for Qubes 4.0:
> https://github.com/marmarek/qubes-core-admin-linux/blob/core3-devel/qubesappmenus/__init__.py
> Especially interesting function: appmenus_create.

I should really build myself a 4.0 installation and start hacking on
that instead...

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/CABQWM_BvNbC4f8-rCxXPDTysVN_kNA0kdLiFKCy-7n7WsJ5d6g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to