I don’t know how many packages y’all install in your systems, but in my case, its quite a few. I run updates only on Fridays nowadays to avoid update “fatigue”. I used to run updates twice a day when running vanilla Arch but that became too much.
So how often do you update your packages?
Edit: I feel like I do not want to automate the process because I want to see what packages are being updated in case something breaks, I want to see whats going on. Pet peeve of mine with automatic hands free updates.
In all honesty, I’m probably addicted to updating. It’s one of the reasons I love Arch so much. If I don’t get a notification that I have any updates available, I usually check for updates at least once every few hours.
Here are two threads on this subject if anyone wishes more opinions and advice on this.
I think there is at least one more tucked away somewhere in the dark nether regions of old topics.
Whenever it comes to mind. With the update notifier in EOS that means I probably update more often than I used to though on my servers I usually do it every week or so but on my lappy it’s never more than 2 or 3 days and usually multiple times a day.
So I actually disabled it, because it was too much, every hour or so I got update notifications, which is why it prompted this post. I just cannot see pending notifications or it will drive me mad.
For me it’s whenever I happen to be using the machine. I may have a bit of a problem with liking to test out hardware, so I have 6 laptops, so they don’t all get turned on every day. Or sometimes every week. Or once in a LONG time they don’t even each get turned on once every month.
The rate of change of packages (i.e. Updates ) is directly proportional to the Network speed which is inversely proportional to the time in 24 hours format
Explanation
My network speed tops at 12 AM and decreases after 6AM . So if I am awake in that time I will update for sure , once or twice a day . If I am not then it may take 2-3 days to update (kernel updates or something big )
#!/usr/bin/env bash
reboot="(ucode|cryptsetup|linux|nvidia|mesa|systemd|wayland|xf86-video|xorg)"
updates=$(checkupdates; yay -Qua)
echo "$updates"
if [[ $updates =~ $reboot ]]; then
echo "Needs reboot .."
fi
When I remember to do it, typically every two or three days.
I check the updates first by running checkupdates; yay -Qua which I have aliased to cu and if something catches my eye and I want it, I run an update. Or before installing any new software.
I find that notifiers can be a bit intrusive - so I found a way to have the information constantly displayed. That way there is no intrusive pop-up - and if I want to know, I can check my conky for ‘whether’, and another conky for ‘what’ (scrolling list of ‘available’). To each his own! Actual updates depend on how many, how long since on that distro, and mood!
I would not bet my life on this as a definitive check whether a reboot is necessary after an update. It is likely to have a few false positives and a few false negatives.
But it’s a fairy decent approximation.
I like your changes to the script, and I think I’m going to replace my alias with that. I am only going to change the checkupdates line to this:
on my servers I usually do it every week or so but on my lappy it’s never more than 2 or 3 days and usually multiple times a day.
.
