| 1 |
On Wednesday 10 July 2002 21:24, Andreas Kotowicz wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I just did a "emerge --update world --emptytree" and due to a time sync |
| 5 |
> it stopped after about 90% of all packages (and 1 day of compiling). If |
| 6 |
> I now rerun "emerge --update world --emptytree" it wants to recompile |
| 7 |
> the whole thing again. why doesn't it write down to some file which |
| 8 |
> packages have been finished so the remaining ones can be done? or is |
| 9 |
> this maybe a bug - or even wanted? |
| 10 |
> |
| 11 |
|
| 12 |
It is "predictable" behaviour and such not a bug. What you could do is get a |
| 13 |
list of everything to be included in the compile, and put it in a file (after |
| 14 |
removing the colors) |
| 15 |
Then you could make some smart grep on the emerge log (you did log, didn't you |
| 16 |
;-) ) to check everything that has allready been compiled. Subtract those |
| 17 |
files (remove every compiled package from the world file) and supposed the |
| 18 |
filename is TOBUILD you do a |
| 19 |
emerge `cat TOBUILD` |
| 20 |
|
| 21 |
Paul |
| 22 |
|
| 23 |
ps. I thought renaming the /var/db/pkg directory and doing an emerge -u world |
| 24 |
should also work, but for me (the pretend) it only wants to emerge system. |
| 25 |
Could that be a bug? |
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
Paul de Vrieze |
| 30 |
Junior Researcher |
| 31 |
Mail: pauldv@××××××.nl |
| 32 |
Homepage: http://www.devrieze.net |
Archives