public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] net-libs/nodejs
Date: Thu, 7 Jul 2022 08:13:57 +0100	[thread overview]
Message-ID: <20220707081343.6b8803ec@digimed.co.uk> (raw)
In-Reply-To: <20220707005118.6af0d5b7@ventiloplattform.tastytea.de>

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

On Thu, 7 Jul 2022 00:51:18 +0200, tastytea wrote:

> > When emergings with --skipfirst (i.e. skip nodejs),
> > I get:
> > emerge: It seems we have nothing to resume...
> > 
> > Checking dependancies:
> > # emerge -vc net-libs/nodejs
> > 
> > Calculating dependencies  .... done!
> >   net-libs/nodejs-14.19.0 pulled in by:
> >     www-client/firefox-91.9.0 requires >=net-libs/nodejs-10.23.1
> > 
> > So, why don't emerge build the other 100'ish packages ?
> > Last time I did emerge nodejs, must I run emerge @world
> > and let that fail first ?  
> 
> Yes, --resume will always try to resume the last command that failed,
> as far as i know.

--keep-going would do what you want, portage tries to emerge whatever
else it can from the list after a failure. But that still means waiting
for nodejs to fail, so I would ass "--exclude nodejs" to your emerge
world command to get everything else sorted, then come back to deal with
nodejs later.


-- 
Neil Bothwick

*Libra*: /(Sept 23--Oct 23)/ An unfortunate typo on your application
results in your being accepted into the Legion Of Superherpes.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-07-07  7:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 22:19 [gentoo-user] net-libs/nodejs karl
2022-07-06 22:51 ` tastytea
2022-07-06 23:34   ` emerge --keep-going didn't continue (Re: [gentoo-user] net-libs/nodejs) karl
2022-07-06 23:41     ` Jack
2022-07-07  7:13   ` Neil Bothwick [this message]
2022-07-18 22:34   ` [gentoo-user] net-libs/nodejs karl
2022-07-07  8:47 ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220707081343.6b8803ec@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox