| 1 |
Patrick Lauer wrote: |
| 2 |
> And if you really absolutely have to do that you can change the sync |
| 3 |
> location on every disruptive change, but (imo) that should be |
| 4 |
> avoided. |
| 5 |
|
| 6 |
If mirroring and other practical concerns weren't an issue what you're |
| 7 |
essentially describing is just moving to a CVS/git/etc repository and |
| 8 |
using such a tool to do all the syncs (ie not using rsync at all). Then |
| 9 |
all you need is an update page that has a list of commands like: |
| 10 |
|
| 11 |
emerge --sync --date "2008-01-01" |
| 12 |
|
| 13 |
emerge -u world |
| 14 |
|
| 15 |
emerge --sync --date "2008-08-10" |
| 16 |
|
| 17 |
Follow this xorg update doc: <link> |
| 18 |
|
| 19 |
emerge --sync --date "2034-04-02" |
| 20 |
|
| 21 |
emerge -u portage so that you have support for the finally-approved glep55 |
| 22 |
|
| 23 |
And so on... :) |
| 24 |
|
| 25 |
That actually gives you a best-of-both-worlds option: continue to use |
| 26 |
rsync for normal use to ease distribution, but have a cvs tree that |
| 27 |
anybody can read from which could be used in upgrade guides for |
| 28 |
out-of-date users. |
Archives