I’ve been playing with some ways of giving more control over the update process, thinking more along the lines of the “roll-up” approach I took with manjaro32:
Step
Action
1
Sync from arch32 to unstable
2
Snap to testing
3
Sync to unstable
4
Repeat…
5
Snap from testing to stable
This meant the branches were quite often in sync but it required manual intervention.
current is synced multiple times per day from Arch stable (like, every hour or half-hour). daily is snapped every day, daily-deferred is the repo from yesterday. weekly is snapped every week, weekly-deferred is the repo from last week.
Any thoughts?
Update:
In case anyone is interested, I have set up https://repo.m2x.dev/. Pick a cadence and add to/set as your /etc/pacman.d/mirrorlist:
A major kernel version update or an update to xorg could make one of my computers unbootable since I use nvidia-390xx drivers from the AUR. So I would have to wait before updating until the AUR package gets updated, but this could be a problem if I wanted to install new software (or if I simply forgot and just updated without thinking about it). So I think this could potentially be very useful to people like me. I could use weekly-deferred and in that week, and update to the AUR package is bound to occur, so I would just update everything at once.
It would, at least, remove one thing to think about. It would dull the bleeding edge just slightly, so to speak…
Current … Daily … Daily-Deferred … Weekly … Weekly Deferred … sounds like the frenetic cadence of modern life! No time! Busy … sometime have to fast track.
I mean. . . if we want to get technical, I really just type topgrade then password and go make a drink and when I come back, I get to find out if I’m hitting the forum, or hitting the wiki and restoring from timeshift.