On Tue, Sep 17, 2019 at 09:01:47AM +0100, [email protected] wrote: > Marc Espie writes: > > I'm a bit surprised nobody looked at instrumenting what sets are actually > > installed on a machine during install/manual upgrade and cloning that > > into sysupgrade to avoid this kind of surprise... > > I mentioned the possibility wrt. syspatch but it was rejected in favour > of expecting users to run a default system or, in effect, become > developers. Not a stance I entirely agree with but which nevertheless > has its merits.
But sysupgrade is a much "simpler" mechanism than syspatch. More importantly, - sysupgrade is definitely about the sets - if you have a non default installation, syspatch happens *at user level* so you have every opportunity to figure out what's going on. Where sysupgrade ? reboot the machine, see your disks overflow. Boom machine kaput.
