Documentation / recommendations about automatic updates

[WildPenquin]

Hi!

I like aurto, it seems to fit quite will into my workflow.

However, I find it's default services a bit too intrusive - namely, updating the repo on every startup and upgrading all cvs packages daily.

Now, in my use case the computer is a desktop computer. I might be doing something graphics sensitive - working, gaming, organizing things or whatever - and definitely don't want a huge compile to start in the background when I actually need the computer.

What I'm suggesting is documentation about how to disable the default behavior, and perhaps a few alternatives or recommendations for different kind of use cases (for example: change time to one where the computer is not used etc.; use cron instead or whatever). IMHO the default should be something less intrusive (i.e. disabled), but maybe that's just me. It's good there is the facility to do it available but perhaps it should be opt-in?

My goal: I don't want any automatic updates from AUR, but to trigger all updates manually (only). I've disabled all services and timers which came with aurto.

[alexheretic]

I think a lot of what aurto provides is the opinionated default setup of aurutils, including automatic update.

It's true that the systemd timers can be disabled or modified and that shouldn't be broken by updates. I wouldn't mind documenting that in the readme.

But ultimately aurto isn't aimed at maximising flexibility because aurutils already does that. Generally I'd say the more you diverge from the default aurto setup the more attractive using aurutils directly becomes.