Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upIdea: qvm-sync-appmenus also parsing /usr/local/share/applications #4152
Comments
t4777sd
changed the title from
qvm-sync-appmenus also parsing /usr/local/share/applications
to
Idea: qvm-sync-appmenus also parsing /usr/local/share/applications
Jul 27, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
t4777sd commentedJul 27, 2018
•
edited
Edited 1 time
-
t4777sd
edited Jul 27, 2018 (most recent)
-
t4777sd
created Jul 27, 2018
Qubes OS version:
4.0
Affected component(s):
Application menu syncing
Steps to reproduce the behavior:
Install any locally installed app that a user may want in a particular VM, but not other VMs and they do not want to make it installed in all VMs and make a bunch of clones of VMs (as that creates its own problems)
Desktop file will be placed in /usr/local/share/applications
Sync the app menu and you will see it does not detect the apps
Expected behavior:
It would be nice if desktop files also looked in /usr/local/share/applications. This provides a mechanism to install software locally without making a lot of template clones.
I understand why ~./.local/share/applications is excluded because it appears some apps install to both that and /usr/share/applications so that would require trying to parse out duplicates etc.
However, no packaged apps install into /usr/local/share/applications and that folder is local to the AppVM too.
Motivation for locally installed apps
The primary motivation is because a single change does not warrant a template clone as that creates a bunch of other issues (resource issues, menu cluttering issues, etc).
The appvm wants to run a different version of software than those in other appvms
The application is less trusted so better to keep it entirely contained in the appvm
The software only belongs in one appvm and its not efficient to create a new template just because of that one software
The software is downloaded from the internet, only belongs in oen appvm, and it makes little since to transfer it to the templatevm (as that has no internet to download it) when it can just be kept in that appvm which is the only place it should run.