public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Drake Wyrm <wyrm@haell.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] cloning systems across architectures
Date: Thu, 11 Mar 2004 07:03:55 -0800	[thread overview]
Message-ID: <20040311150355.GB21609@phaenix.haell.com> (raw)
In-Reply-To: <200403111046.55363.jstubbs@gentoo.org>

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

On Thu, 2004-03-11, 10:46:55 +0900, in
<200403111046.55363.jstubbs@gentoo.org>, Jason Stubbs
<jstubbs@gentoo.org> wrote:
> On Thursday 11 March 2004 08:25, George Shapovalov wrote:
[snip]
> Emerge now checks to see if a package listed in the world file is
> installed before doing anything with it. If it's not installed, it is
> skipped.

I've noticed.

I can see three ways portage could respond to additions to the world
file:

	1. skip the added package
	2. install the added package
	3. abort due to state file inconsistency

Of the three, I would select #2. I would be hard-pressed to choose
between #1 and #3 as the lesser of two evils. My initial instinct is to
avoid arbitrary crashes, but if installing packages found in the world
file is dangerous, perhaps a stronger reaction may be in order.

Perhaps somebody could seed my memepool on this issue.

-- 
Batou: Hey, Major... You ever hear of "human rights"?
Kusanagi: I understand the concept, but I've never seen it in action.
  --Ghost in the Shell

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2004-03-11 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10 20:44 [gentoo-portage-dev] cloning systems across architectures Anthony Dodson
2004-03-10 22:02 ` Pieter Van den Abeele
2004-03-10 23:25 ` George Shapovalov
2004-03-11  1:46   ` Jason Stubbs
2004-03-11 15:03     ` Drake Wyrm [this message]

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=20040311150355.GB21609@phaenix.haell.com \
    --to=wyrm@haell.com \
    --cc=gentoo-portage-dev@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