From owner-freebsd-ports@FreeBSD.ORG Mon Mar 3 21:40:30 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 667BE10656C2 for ; Mon, 3 Mar 2008 21:40:30 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id 36AEF8FC15 for ; Mon, 3 Mar 2008 21:40:30 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (nat-wh-1.rz.uni-karlsruhe.de [129.13.72.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id ABF30405BBB; Mon, 3 Mar 2008 22:40:28 +0100 (CET) Message-ID: <47CC704C.1010106@bsdforen.de> Date: Mon, 03 Mar 2008 22:40:28 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.12 (X11/20080303) MIME-Version: 1.0 To: RW References: <47CBC3C5.9050007@bsdforen.de> <20080303155354.2043d131@gumby.homeunix.com.> <47CC49B8.6080501@bsdforen.de> <20080303213454.53f29198@gumby.homeunix.com.> In-Reply-To: <20080303213454.53f29198@gumby.homeunix.com.> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: interactive ports - the plague 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: Mon, 03 Mar 2008 21:40:30 -0000 RW wrote: > On Mon, 03 Mar 2008 19:55:52 +0100 > Dominic Fandrey wrote: > >> RW wrote: >>> On Mon, 03 Mar 2008 10:24:21 +0100 >>> Dominic Fandrey wrote: >>> > >>>> I cannot find any policy on interactive ports in the Porters' >>>> Handbook. Maybe there aught to be one. >>> Setting BATCH is supposed to prevent genuinely interactive ports >>> from building (that's actually the original purpose of BATCH). >> But this will also keep the config screens away from me, which can be >> handled before all builds quite comfortably. > > Not if you do the config screens before setting BATCH. True, I suppose my make.conf will get a couple of new .if blocks.