1 |
On Sun, Apr 19, 2020 at 01:03:55PM +0200, Gerion Entrup wrote: |
2 |
> Portage then often stops, saying a dependency keyword is missing or a |
3 |
> useflag etc. However, this always happens incident after incident, so I |
4 |
> need to run portage multiple times. |
5 |
> |
6 |
> Is there a way to instruct portage to just say: "Ok, here is a |
7 |
> configuration fix necessary, maybe a use flag must be added, but let's |
8 |
> assume, the user does this and the use flag is set now. What do I need |
9 |
> to do next." |
10 |
|
11 |
Have you seen the --skipfirst option, to be used in conjunction with --resume |
12 |
(-r) ? Taking directly from the man page of emerge: |
13 |
|
14 |
--skipfirst |
15 |
This option is only valid when used with --resume. It removes |
16 |
the first package in the resume list. Dependencies are |
17 |
recalculated for remaining packages and any that have |
18 |
unsatisfied dependencies or are masked will be automatically |
19 |
dropped. Also see the related --keep-going option. |
20 |
|
21 |
--resume, -r |
22 |
Resumes the most recent merge list that has been aborted due to |
23 |
an error. This re-uses the arguments and options that were |
24 |
given with the original command that's being resumed, and the |
25 |
user may also provide additional options when calling |
26 |
--resume. It is an error to provide atoms or sets as arguments |
27 |
to --resume, since the arguments from the resumed command are |
28 |
used instead. Please note that this operation will only return |
29 |
an error on failure. If there is nothing for portage to do, |
30 |
then portage will exit with a message and a success condition. |
31 |
A resume list will persist until it has been completed in |
32 |
entirety or until another aborted merge list replaces it. The |
33 |
resume history is capable of storing two merge lists. After one |
34 |
resume list completes, it is possible to invoke --resume once |
35 |
again in order to resume an older list. The resume lists are |
36 |
stored in /var/cache/edb/mtimedb, and may be explicitly |
37 |
discarded by running `emaint --fix cleanresume` (see emaint(1)). |
38 |
|
39 |
Sorry if I've misunderstood your intentions; the wording of your |
40 |
question was a little difficult for me to comprehend, but I think this |
41 |
is what you want ;-) |
42 |
|
43 |
-- |
44 |
|
45 |
Ashley Dixon |
46 |
suugaku.co.uk |
47 |
|
48 |
2A9A 4117 |
49 |
DA96 D18A |
50 |
8A7B B0D2 |
51 |
A30E BF25 |
52 |
F290 A8AA |