@Iolaum you can currently set
snapd to only refresh snaps once per month as per the docs I linked above. However I know that’s not quite what you’re looking for…I wonder if
snapd can get closer to what you’re looking for without using a global off switch though:
snapd could support an option that, when selected, means that
snapd doesn’t automatically refresh for a month after the last manual refresh. That way @Iolaum can refresh only when they turn off their computer, as long as they do that once per month?
@Iolaum if you read what @niemeyer (the snapd lead) has said earlier in this thread (quite close to the start but also throughout), they’re not producing an off switch because they don’t want users to be stuck on outdated and insecure software. By not producing the off switch, they’re forcing themselves to grow features (like maybe the one I suggested above) which mean that users should never need an off switch. It’s not being kept ‘simple’, as you see it, because they want updated systems that are usable, which means somewhat complex (but very useful) policy.
Why can’t you work and update simultaneously though, not enough bandwidth?
As far as I know, snap updates don’t have changelogs anyway, @niemeyer is this an option that devs should be able to give? Perhaps someone could choose to configure
snapd so that after
snap refresh is run, before refreshing, all the changelogs come up for confirmation? Or,
snapd could require that users refresh when
refresh is run but provide the changelogs somewhere for access. Also how do you define ‘misbehaves’ @Iolaum?