My question relates primarily to Arch Linux, but I imagine that it could be generalized to any rolling release distribution.
Is there a standard method for updating when one is far behind the current "updated release"?
With rolling releases, it is usually bad to go without updating for extended periods of time (say a month or two.) But what happens if you're unable to update because of lack of internet or time (e.g: study/vacation abroad)?
The problem is the following:
- there are a lot of config files that need changing all at once.
- with more packages updating, its harder to figure out which one breaks something.
So we'd want to somehow reduce the amount of packages being updated. Could any of the following possible solutions work to solve this problem?
Solution 1: Update to a certain date or only so far at one time.
So if I was behind by a month, could I update one week at a time (3 weeks ago, 2 weeks ago, 1 week ago, current) thereby reducing the changes happening at once and making the update manageable?
If you knew in advance that you would want to do this then could you setup a server to take snapshots of the mirrors every day/week? So later you know how to update to that point in time?
Solution 2: Get a list of packages that have been updated and update each package one at a time.
This would work as long as the dependencies didn't get to intertwined and force you to update everything at once anyways.
EDIT: describe problem explicitly, added solution