| 1 |
Am Sun, 3 Dec 2017 04:26:55 +0100 |
| 2 |
schrieb tuxic@××××××.de: |
| 3 |
|
| 4 |
> If the compilation will fail at a certain point (and it will fail, |
| 5 |
> since this is a complete new thing) -- would it be possible to resume |
| 6 |
> even some tweaks, hacks and patches (even certain recompilations) |
| 7 |
> would be needed in between? |
| 8 |
|
| 9 |
Just run `emerge -e --keep-going y @world`. |
| 10 |
|
| 11 |
> Can I stop a running emerge @world and resume later? |
| 12 |
|
| 13 |
Maybe with `emerge --resume`. But I don't know if interrupting this |
| 14 |
would cause some problems in this particular case. |
| 15 |
|
| 16 |
> How does a restarted emerge @world recognizes packages, which are |
| 17 |
> already compiled according to the new standard? |
| 18 |
|
| 19 |
It simply creates a list of the packages to be installed as usual and |
| 20 |
knows which of them are already installed and which are not. Then it |
| 21 |
recalculates the dependency tree as usual. |
| 22 |
|
| 23 |
Heiko |
Archives