public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Laurence Perkins <lperkins@openeye.net>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] Reinstall
Date: Wed, 11 May 2022 20:34:40 +0000	[thread overview]
Message-ID: <MW2PR07MB40588E7AC9AF73F8F1F61DA3D2C89@MW2PR07MB4058.namprd07.prod.outlook.com> (raw)
In-Reply-To: <20220511193442.29dad2fc@digimed.co.uk>

> -----Original Message-----
> From: Neil Bothwick <neil@digimed.co.uk> 
> Sent: Wednesday, May 11, 2022 11:35 AM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] Reinstall
> 
> On Wed, 11 May 2022 16:45:31 +0000, Laurence Perkins wrote:
> 
> > Alternatively, fully update the system before putting in your world 
> > file, and then instead of copying in the world file all at once just 
> > run a loop to emerge the lines in it one at a time.
> 
> Now you mention it, that's what I did last time, although my loop emerge ten lines at a time to cut down on the number of dependency recalculations.
> 
Well, and have it check the exit status and spit any lines that fail into another file to try again later.  Then shuffle the new file so the bad ones move around, or do the second pass one at a time.

LMP


  reply	other threads:[~2022-05-11 20:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  9:57 [gentoo-user] Reinstall Francisco Ares
2022-05-11 11:06 ` Michael
2022-05-11 12:26 ` David Palao
2022-05-11 16:45   ` Laurence Perkins
2022-05-11 18:34     ` Neil Bothwick
2022-05-11 20:34       ` Laurence Perkins [this message]
2022-05-11 20:51       ` Wols Lists
2022-06-19 16:23         ` Francisco Ares
2022-06-19 17:22           ` [gentoo-user] Reinstall Grant Edwards
2022-06-19 17:32             ` Michael
2022-06-19 18:26               ` Francisco Ares
2022-06-20  5:01                 ` Bill Kenworthy
2022-06-19 18:08             ` Francisco Ares
2022-06-20 17:28           ` [gentoo-user] Reinstall Laurence Perkins
2022-05-11 14:32 ` 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=MW2PR07MB40588E7AC9AF73F8F1F61DA3D2C89@MW2PR07MB4058.namprd07.prod.outlook.com \
    --to=lperkins@openeye.net \
    --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