Open EdGeraghty opened 3 months ago
Some binary prefs like disable_updates
came be added to qubes to manage this feature. Looks useful as some qubes (offline) with fixed version of software can indeed be expected not to be updated.
I wonder if this is what the updateable
preference is for. The docs don't clarify much about the intended purpose:
updateable True if this machine may be updated on its own.
However it cannot be changed by the user. I wonder what the reasoning is (maybe footshooting prevention).
[user@dom0 ~]$ qvm-prefs fedora-39-xfce updateable False
qvm-prefs: error: property 'updateable' on TemplateVM instance cannot be set
The problem you're addressing (if any)
I have several qubes which are never going to receive updates - currently these qubes are visible in the update manager, but they are clutter
The solution you'd like
The ability to hide (a) qube(s) from the updating functionality
The value to a user, and who that user might be
It means we can select all in the update manager rather than having to choose qubes individually. This will benefit anyone running a Windows 10/11 HVM, TempleOS, or a number of other guests such as the mirage-os unikernel.