From owner-freebsd-ports@FreeBSD.ORG Sat Mar 3 13:51:31 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CED211065677 for ; Sat, 3 Mar 2012 13:51:31 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 4D6658FC08 for ; Sat, 3 Mar 2012 13:51:30 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so2190212wgb.31 for ; Sat, 03 Mar 2012 05:51:30 -0800 (PST) Received-SPF: pass (google.com: domain of rwmaillists@googlemail.com designates 10.180.95.34 as permitted sender) client-ip=10.180.95.34; Authentication-Results: mr.google.com; spf=pass (google.com: domain of rwmaillists@googlemail.com designates 10.180.95.34 as permitted sender) smtp.mail=rwmaillists@googlemail.com; dkim=pass header.i=rwmaillists@googlemail.com Received: from mr.google.com ([10.180.95.34]) by 10.180.95.34 with SMTP id dh2mr4060543wib.15.1330782690096 (num_hops = 1); Sat, 03 Mar 2012 05:51:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=Mwr0CGriflkcsFAspduTPTqr0djuW6uEnoAW95tveww=; b=imAG4BEXki/37CqPfY8k/e+5x/DC0EgGvq3mWceL0TV3z7toFvTJrpnG7bixnV1jQY yM8t3qPUNv44XDbXaYLrjlVwG46t0AEmr79WH4T4FV18NQuZvjm9LntvPHpUXY9W0sSM CJT+0wUGFkc0DpM5JMw0zRY2+PYYf+DKUfwvDdeNUj737oVsqKnITILL3NtHxF40Xssb VYuFuxgmJy9SQrtQ8q5O0IXLNR+Mjkc488QU7mdZFC1Ql3JbNDPdOavSSBnAkKSEz7As LprtuXOt3MsSqDTQ9HJ0vy0GNgWm3WJdme5/iJJv3u1LaD2RCbLUP58Vhfhk59irXWQf K6lQ== Received: by 10.180.95.34 with SMTP id dh2mr3210243wib.15.1330782690044; Sat, 03 Mar 2012 05:51:30 -0800 (PST) Received: from gumby.homeunix.com (87-194-105-247.bethere.co.uk. [87.194.105.247]) by mx.google.com with ESMTPS id h19sm9553343wiw.9.2012.03.03.05.51.27 (version=SSLv3 cipher=OTHER); Sat, 03 Mar 2012 05:51:28 -0800 (PST) Date: Sat, 3 Mar 2012 13:51:25 +0000 From: RW To: ports@freebsd.org Message-ID: <20120303135125.7979b6a8@gumby.homeunix.com> In-Reply-To: <20306.2907.309020.842953@jerusalem.litteratus.org> References: <4F4BA7CE.20107@FreeBSD.org> <20120303010602.6daeb272@cox.net> <4F51D392.8080605@FreeBSD.org> <20306.2907.309020.842953@jerusalem.litteratus.org> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: portupgrade -> portmaster Rosetta Stone? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2012 13:51:32 -0000 On Sat, 3 Mar 2012 07:15:23 -0500 Robert Huff wrote: > > Doug Barton writes: > > > On 3/2/2012 11:06 PM, Conrad J. Sabatier wrote: > > > Doug, is there a way to emulate portupgrade's "-k" (keep going) > > > option, to have the remaining list of ports to be built still > > > continue processing even if one port's build fails? > > > > You haven't missed it, the answer is no. It's part of that > > "portmaster can't read minds" problem that if something fails, I > > have no way of knowing if the rest of the updates should stop as > > a result. > > But ... isn't this a case where you don't have to read minds? > It seems (to me) the user would be saying "I understand the risk, > and accept responsibility for dealing with the consequences.". At > that point, whether thet're right or wrong is not your problem .... I think it worth pointing out that portupgrade has two levels of "keep going". By default portupgrade (and portmanager) will continue with any port that doesn't depend on a failed port. This is more or less what would have happened if it terminated on the first error, but you had been luckier with the arbitrary part of the build order. The minus -k flag allows it to build the rest as well. When you finally fix the failed ports you end up with ports built out of dependency order. In my experience it's the default "keep going" that's most useful because it means that portupgrade usually completes most of what it needs to do even if it fails on the first port.