From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 3962C1381F3 for ; Sun, 2 Dec 2012 14:17:11 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0427121C004; Sun, 2 Dec 2012 14:16:52 +0000 (UTC) Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 507EBE05C1 for ; Sun, 2 Dec 2012 14:15:10 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id hq12so559712wib.4 for ; Sun, 02 Dec 2012 06:15:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:organization :x-mailer:mime-version:content-type:content-transfer-encoding; bh=W1HPiXpCOlUFKzzki1eExZ3FqRB5hnHsiY6Uiozdvw4=; b=ga4TRhgsnL5kj6mfYqu8mOL53WXh9+lC7ZeYNd9d1oAJR3LtSXIQafQplHt+lEUwIH sFooP3CSmqt9zfmHBayDOPbatA1kEPRjXdO8CpgD+2sz2yE9nhssoBS/0n2mWlbKJ/pO cZKTO9i+RU/1n2HILp7f+Vn86gauMh2t6tDwTR7b355nODV+QBSmyypPUh5OT9XuKzNU TMreNsV9ly1jnByVCRjOUNsD5YSZVjKqJRC6rslCQX3Z5JKD0uuLh68rv70GZMhfql23 t3IAbRZPstC5IZf9vBskqVy82Vx7aYaeqoimJJgFzDuPy8wfpYSY18gxF3k5ZVUU/jGV Mlzg== Received: by 10.216.70.138 with SMTP id p10mr2562253wed.47.1354457708902; Sun, 02 Dec 2012 06:15:08 -0800 (PST) Received: from khamul.example.com (196-209-227-124.dynamic.isadsl.co.za. [196.209.227.124]) by mx.google.com with ESMTPS id dw4sm8065214wib.1.2012.12.02.06.15.06 (version=SSLv3 cipher=OTHER); Sun, 02 Dec 2012 06:15:07 -0800 (PST) Date: Sun, 2 Dec 2012 16:12:02 +0200 From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] emerge --update : how to keep it going? Message-ID: <20121202161202.05923071@khamul.example.com> In-Reply-To: <87ehj94k96.fsf@einstein.gmurray.org.uk> References: <1354278367.13959.0@numa-i> <50B8E26E.6020907@orlitzky.com> <3685331.7YM97IiLFU@atom> <33863279.yiiX5jZFcB@energy> <87ehj94k96.fsf@einstein.gmurray.org.uk> Organization: Internet Solutions X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 627cd3b2-5b97-4dd8-a47c-dc12a663af32 X-Archives-Hash: fc0b23b6656fdb59b35c42628feb9d8f On Sat, 01 Dec 2012 19:58:45 +0000 Graham Murray wrote: > Volker Armin Hemmann 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. > That is a terribly bad idea, and you need to have a fairly deep understanding of IT theory to see it (which is why so few people see it). I don't know which camp you are in. The command is to emerge world, and it's supposed to be determinate, i.e. when it's ready to start you can tell what it's going to do, and that should be what you told it to do, no more and no less[1] the command is "emerge world" not "emerge the-bits-of-world-you-think-you-can-deal-with" If portage cannot emerge world and fully obey what root told it to do, then portage correctly refuses to continue. It could not possibly be any other way, as eg all automated build tools (puppet, chef and friends, even flameeyes's sandbox) break horribly if you do it any other way. Life is hard enough dealing with build failures without adding portage do somethign different to what it was told into the mix. [1] "determinate" excludes build failures, as those are not predictable. Dep graph failures happen before the meaty work begins. -- Alan McKinnon alan.mckinnon@gmail.com