| 1 |
As was pointed up above, yes, you can inerrupt and resume builds. |
| 2 |
To interrupt use... you won't believe me, Ctrl-C at any time ;). |
| 3 |
|
| 4 |
Portage registers installed packages (including lists of installed files and a |
| 5 |
bunch of other information) in the database as it goes along. So, when you |
| 6 |
run emerge again, it will pick up from the last package it was building. You |
| 7 |
will have to specifically force rebuild of *all* packages that are required |
| 8 |
for the one you are emerging if you so desire.. |
| 9 |
Therefore it is not necessary to emerge system package by package. Though this |
| 10 |
might be usefull during bootstrap (the precedeeng step), however even in this |
| 11 |
case it is IMHO easier to modify the script itself.. |
| 12 |
|
| 13 |
Now, there is the issue of that last package, that was interrupted. |
| 14 |
emerge --resume will only restart last emerge command, it will not pick up |
| 15 |
from where the compilation was interrupted. |
| 16 |
Instead you should consider using ccache (just emerge it, portage will see and |
| 17 |
use it. You might want to set CCACHE_DIR though). This will cache all |
| 18 |
compiles made by gcc, and thus significantly cut duplicated compile time. |
| 19 |
|
| 20 |
Also, if you have access to more boxes on a local LAN, you can try using |
| 21 |
distcc - this will distribute compile tasks to all involved hosts.. |
| 22 |
|
| 23 |
George |
| 24 |
|
| 25 |
|
| 26 |
On Sunday 06 April 2003 17:59, Paulo da Silva wrote: |
| 27 |
> I am about to give gentoo a try. |
| 28 |
> Because of my relatively slow CPU, I would like to interrupt |
| 29 |
> the compilation process and be able to resume it later. |
| 30 |
> Is there a way to do that? If there are any docs where this is |
| 31 |
> described, pls just tell me how/where to get them. |
| 32 |
> |
| 33 |
> TIA |
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-dev@g.o mailing list |
Archives