@niemeyer: I installed a Rocket.Chat server a few weeks ago and the use of Snapcraft seemed great at first. Then suddenly LDAP authentication stopped working for new users that didn’t log in previously, debugging indicates some bug or something (The user is clearly found, but then it says “User not found”).
Now I have no reasonable easy way of knowing whether it was an update that broke it or something else.
Delaying updates will not fix this, there needs to be a simple way to turn it off completely.
Some random other example: Perhaps I’d like to do some staged rollout with some custom script or whatever, first deploying to one system and then slowly continuing. Autoupdate would interfere.
Autoupdate is a great feature for some use cases, but why should anyone care if I turn it off? Open source is all about putting the user in control, the current way of working does exactly the opposite. Even if I wanted to shoot myself in foot, why disallow it? Why care? Samsung, Huawei, Google, Ubuntu etc. all allow users to turn off updates. Why not?
Windows 10 is working like you describe and people hate it…
If I see the length of the threads about this subject, then it’s inevitable that a disable switch will be included at some point… Why care? Why not just include it now and move on? Demand for a disable switch will only increase as the popularity of snapcraft grows.
I’ll just block it by pointing api.snapcraft.io to 127.0.0.1 in the hosts file for now as a workaround, but I’d prefer to do it through a global switch in the future.
Anyway, that’s just my view on it, thanks for the great stuff you’re doing!
Kindest regards, Don