| 1 |
On Sat, 01 Dec 2012 19:58:45 +0000 |
| 2 |
Graham Murray <graham@×××××××××××.uk> wrote: |
| 3 |
|
| 4 |
> Volker Armin Hemmann <volkerarmin@××××××××××.com> writes: |
| 5 |
> |
| 6 |
> > --keep-going does not help you, if the emerge does not start |
| 7 |
> > because of missing dep/slot conflict/blocking/masking whatever... |
| 8 |
> |
| 9 |
> Though it would be nice if there was some flag, probably mainly of use |
| 10 |
> with either ' -u @world' or --resume, to tell portage to get on and |
| 11 |
> merge what it can and leave any masked packages or those which would |
| 12 |
> generate blockers or conflicts. |
| 13 |
> |
| 14 |
|
| 15 |
That is a terribly bad idea, and you need to have a fairly deep |
| 16 |
understanding of IT theory to see it (which is why so few people see |
| 17 |
it). I don't know which camp you are in. |
| 18 |
|
| 19 |
The command is to emerge world, and it's supposed to be determinate, |
| 20 |
i.e. when it's ready to start you can tell what it's going to do, and |
| 21 |
that should be what you told it to do, no more and no less[1] |
| 22 |
|
| 23 |
the command is |
| 24 |
"emerge world" |
| 25 |
not |
| 26 |
"emerge the-bits-of-world-you-think-you-can-deal-with" |
| 27 |
|
| 28 |
If portage cannot emerge world and fully obey what root told it to do, |
| 29 |
then portage correctly refuses to continue. It could not possibly be |
| 30 |
any other way, as eg all automated build tools (puppet, chef and |
| 31 |
friends, even flameeyes's sandbox) break horribly if you do it any |
| 32 |
other way. Life is hard enough dealing with build failures without |
| 33 |
adding portage do somethign different to what it was told into the mix. |
| 34 |
|
| 35 |
[1] "determinate" excludes build failures, as those are not predictable. |
| 36 |
Dep graph failures happen before the meaty work begins. |
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
Alan McKinnon |
| 42 |
alan.mckinnon@×××××.com |
Archives