1 |
Peter Campion-Bye wrote: |
2 |
|
3 |
>Hi, |
4 |
>Trying to do an 'emerge -e world' I come up against the odd package that |
5 |
>doesn't build without some intervention. I know I can do 'emerge --resume |
6 |
>--skipfirst' and carry on, but sometimes the broken package could be built ok |
7 |
>with a little intervention, for example, my build breaks on pilot-link, which |
8 |
>can be simply fixed with 'FEATURES="-sandbox" emerge pilot-link'. Problem is, |
9 |
>I can't do a resume after this as the emerge list from the world build has |
10 |
>been blatted when I emerged pilot-link. So, is there any way I can preserve |
11 |
>the state of the world build, so that after building the breaking package I |
12 |
>can do a --resume --skipfirst and carry on with the world build? |
13 |
>Any other suggestions for workarounds? |
14 |
>thanks |
15 |
> |
16 |
> |
17 |
|
18 |
I did this once. I renamed the emerge.log then did what needed doing |
19 |
and then put the back-up back to it's original name, erasing the little |
20 |
that was generated while fixing something. It may not work in every |
21 |
case though but it may be worth a try. |
22 |
|
23 |
Dale |
24 |
:-) |
25 |
:-) |
26 |
-- |
27 |
gentoo-user@g.o mailing list |