You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Lubuntu, we want to have a live system which keeps a default install, but if a certain netboot item is selected, it should remove packages instead of add them.
Also, it would be good to have the selections stored in a global variable.
Lastly, it would be good to be able to specify whether the values should be checkboxes or radio buttons. For Lubuntu, we'd have the latter enabled by default.
I really don't want to have to keep and maintain a custom distro patch for this downstream, but I also wanted to seek feedback on whether I should fork netinstall upstream and make it into what I'm visioning, or if these things could be contributed (and enabled optionally) in the existing module.
The text was updated successfully, but these errors were encountered:
The packages module is used to do the actual changes to the system. It supports remove operations, so that part is ready for you. The trick is to get the netinstall job to do the right thing.
For upstreaming, I'd split this into two PR's: one that handles the UI parts -- changing to radio buttons to handle exclusive groups, for instance -- and one that changes how packages are injected into global storage. The global storage already has a key packageOperations which can contain anything that the package.conf can contain (e.g. also supports remove operations).
For Lubuntu, we want to have a live system which keeps a default install, but if a certain netboot item is selected, it should remove packages instead of add them.
Also, it would be good to have the selections stored in a global variable.
Lastly, it would be good to be able to specify whether the values should be checkboxes or radio buttons. For Lubuntu, we'd have the latter enabled by default.
I really don't want to have to keep and maintain a custom distro patch for this downstream, but I also wanted to seek feedback on whether I should fork netinstall upstream and make it into what I'm visioning, or if these things could be contributed (and enabled optionally) in the existing module.
The text was updated successfully, but these errors were encountered: