On Mon, May 17, 2021 at 10:32:49PM -0500, Sven Semmler wrote: > On 5/17/21 7:14 AM, unman wrote: > > user might be surprised that removing the package that installed > > (e.g) a VPN set-up did not remove it also. > > We could re-frame "formula" as "action" and the packages contain them. > > In this concrete example there would be distinct actions contained in the > package "VPN qube": > > - create VPN qube > - remove VPN qube > > * the package makes the action available > * the action when executed does the changes > > In this context it would be critical that the formula are not executed > automatically when the respective package is installed. Rather there would > be a GUI where those installed actions show up and can then be executed. > > Would that fit with what you are already working on? > > /Sven > > -- > public key: https://www.svensemmler.org/0x8F541FB6.asc > fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 >
I have toyed with that idea, particularly where a state might be applicable to many templates or qubes. (E.g install office packages, or splt-gpg.) My simple use case would be for packages with states like the default ones available on start up. They produce a definite outcome with little interaction. Should this be a generic GUI or one for each package? -- 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 qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/20210518145357.GD3162%40thirdeyesecurity.org.
