Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Software Installation qube #7457

Open
deeplow opened this issue Apr 20, 2022 · 5 comments
Open

Software Installation qube #7457

deeplow opened this issue Apr 20, 2022 · 5 comments
Labels
C: app menu The primary user-facing GUI application menu in Qubes OS C: core C: templates P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience

Comments

@deeplow
Copy link

deeplow commented Apr 20, 2022

The problem you're addressing (if any)

In qubes it's quite hard to install software and the graphical software centers don't work

Proposed Solution (simple version)

An internet-connect disposable qube running Gnome's software center. When the user chooses the software to install, a prompt asks the user on which qube they want to install and then it communicates the package names to that qube. Then that qube proceeds to install it.

Proposed Solution (complex version)

The workflow for the user would start by clicking a install software button on the qubes menu tab for a particular qube:

menu1(1)

By knowing in advance which qube the user wants to install software on, this software installation qube could be created on-demand based on the template on which the qube to be updated is based. This way it would be running the same system and therefore all packages listed would be guaranteed to be compatible. This could be good for example in systems where there are different software stores: suppose in Fedora there is Software Center and in ubuntu there is the Ubuntu Store (no idea if that's the case).

Let's see an example:

  1. user clicks install software on personal qube tab in the qubes menu
  2. starts personal-software-center qube (created on demand and based on Fedora -- the same tempalte as personal)
  3. starts patched Software Center (*) application on personal-software-installer qube
  4. user chooses software to install (e.g. vlc)
  5. personal-software-installer sends package names via qrexec to fedora-34 (the template of personal)
  6. fedora-34 shows a prompt with the package names it received for the user to confirm these are the packages it wants to install

(*)patched software center: (probably) a forked version that has been modified not to actually install software but rather sends the names of the packages to be installed to the app qube or template.

The value to a user, and who that user might be

@deeplow deeplow added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. labels Apr 20, 2022
@deeplow
Copy link
Author

deeplow commented Apr 20, 2022

Then there could be a + install software button on the qubes menu for each qube. This would provide the user of a very clear hint of where they're supposed to do to install software (something that is quite hard to know currently. @marmarta @ninavizz

@andrewdavidwong andrewdavidwong added this to the Release TBD milestone Apr 20, 2022
@deeplow
Copy link
Author

deeplow commented Apr 20, 2022

@fepitre mentioned this is a similar implementation to the way installing software is done in dom0: it's done via sys-firewall.

@deeplow
Copy link
Author

deeplow commented Apr 20, 2022

I've updated the original issue's description to include a more detailed description on how this could be implemented in terms of user workflow.

@nicolaipre

This comment was marked as off-topic.

@deeplow

This comment was marked as off-topic.

@andrewdavidwong andrewdavidwong added ux User experience C: app menu The primary user-facing GUI application menu in Qubes OS labels Mar 6, 2023
@andrewdavidwong andrewdavidwong removed this from the Release TBD milestone Aug 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: app menu The primary user-facing GUI application menu in Qubes OS C: core C: templates P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience
Projects
None yet
Development

No branches or pull requests

3 participants