public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] emerge --update : how to keep it going?
Date: Sat, 1 Dec 2012 12:19:17 -0800	[thread overview]
Message-ID: <CAK2H+efmwFcSFHTu_rwjTs5sAapPJjOJPHsmLySMe=tYowQmYw@mail.gmail.com> (raw)
In-Reply-To: <87ehj94k96.fsf@einstein.gmurray.org.uk>

On Sat, Dec 1, 2012 at 11:58 AM, Graham Murray <graham@gmurray.org.uk> wrote:
> Volker Armin Hemmann <volkerarmin@googlemail.com> writes:
>
>> --keep-going does not help you, if the emerge does not start because of
>> missing dep/slot conflict/blocking/masking whatever...
>
> Though it would be nice if there was some flag, probably mainly of use
> with either ' -u @world' or --resume, to tell portage to get on and
> merge what it can and leave any masked packages or those which would
> generate blockers or conflicts.
>

emerge -fDuN @world

will both check/resolve dependencies as well as insure that all files
required to do the build are downloaded. I typically run this command
prior to emerging anything as I dislike coming back and hour later and
finding the emerge didn't finish because a file either couldn't be
downloaded or its manifest didn't check out.

Just an alternative way to do things.

HTH,
Mark


  reply	other threads:[~2012-12-01 20:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 12:26 [gentoo-user] emerge --update : how to keep it going? Helmut Jarausch
2012-11-30 12:42 ` Francisco Ares
2012-11-30 12:43 ` Michael Mol
2012-11-30 12:46 ` Dale
2012-11-30 12:52 ` Yohan Pereira
2012-11-30 13:05 ` 2sb7vwu
2012-11-30 16:44   ` Michael Orlitzky
2012-12-01 13:02     ` 2sb7vwu
2012-12-01 18:56       ` Volker Armin Hemmann
2012-12-01 19:58         ` Graham Murray
2012-12-01 20:19           ` Mark Knecht [this message]
2012-12-01 20:30             ` Volker Armin Hemmann
2012-12-02 14:12           ` Alan McKinnon
2012-12-02 14:58             ` kwkhui
2012-11-30 17:53 ` Keith Dart
2012-11-30 18:01 ` Helmut Jarausch

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='CAK2H+efmwFcSFHTu_rwjTs5sAapPJjOJPHsmLySMe=tYowQmYw@mail.gmail.com' \
    --to=markknecht@gmail.com \
    --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