1 |
On 2022.07.06 19:34, karl@××××××××.se wrote: |
2 |
> tastytea: |
3 |
> > On 2022-07-07 00:19+0200 karl@××××××××.se wrote: |
4 |
> ... |
5 |
> > > When emergings with --skipfirst (i.e. skip nodejs), |
6 |
> > > I get: |
7 |
> > > emerge: It seems we have nothing to resume... |
8 |
> > > |
9 |
> > > Checking dependancies: |
10 |
> > > # emerge -vc net-libs/nodejs |
11 |
> > > |
12 |
> > > Calculating dependencies .... done! |
13 |
> > > net-libs/nodejs-14.19.0 pulled in by: |
14 |
> > > www-client/firefox-91.9.0 requires >=net-libs/nodejs-10.23.1 |
15 |
> > > |
16 |
> > > So, why don't emerge build the other 100'ish packages ? |
17 |
> > > Last time I did emerge nodejs, must I run emerge @world |
18 |
> > > and let that fail first ? |
19 |
> > |
20 |
> > Yes, --resume will always try to resume the last command that |
21 |
> failed, |
22 |
> > as far as i know. |
23 |
> |
24 |
> Just tried that, emerge world and then killing g++ once the build for |
25 |
> nodejs started and "nodejs" failed, but emerge didn't continue with |
26 |
> the next one (using --keep-going), so why is nodejs blocking |
27 |
> everything |
28 |
> else ??? |
29 |
> |
30 |
> So I removed firefox from world, now the rest is building. I'll solve |
31 |
> the firefox/nodejs thing later. |
32 |
> |
33 |
> Regards, |
34 |
> /Karl Hammar |
35 |
|
36 |
I think you might also want to use --skip-first, which should then also |
37 |
skip firefox due to the missing dependency. You could also use |
38 |
--exclude firefox, to save editing your world file. |