1 |
> * Perhaps the best solution of all is to simply copy your environment to a |
2 |
> "staging" box and perform updates there first (building binary packages |
3 |
> with emerge --buildpkg). After a little testing, you can rapidly install |
4 |
> your known-working packages on your production box (with emerge --usepkg). |
5 |
|
6 |
Another point: sometimes you can even take that sort of approach on a |
7 |
single box by using emerge -B (which builds a binary package without |
8 |
installing it). The downside is that any dependencies which are mandatory |
9 |
must be built _and_ installed for the package to be built with -B! |
10 |
Depending on the situation you're in, it might be enough though. |
11 |
|
12 |
Cheers, |
13 |
|
14 |
--Kerin Francis Millar |