From owner-freebsd-questions@FreeBSD.ORG  Thu Oct 20 01:39:54 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4C2D916A421
	for <freebsd-questions@freebsd.org>;
	Thu, 20 Oct 2005 01:39:54 +0000 (GMT)
	(envelope-from list-freebsd-2004@morbius.sent.com)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com
	[66.111.4.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B28443D64
	for <freebsd-questions@freebsd.org>;
	Thu, 20 Oct 2005 01:39:53 +0000 (GMT)
	(envelope-from list-freebsd-2004@morbius.sent.com)
Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149])
	by frontend1.messagingengine.com (Postfix) with ESMTP id 57A32CD5493
	for <freebsd-questions@freebsd.org>;
	Wed, 19 Oct 2005 21:39:51 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.151])
	by frontend1.internal (MEProxy); Wed, 19 Oct 2005 21:39:51 -0400
X-Sasl-enc: qYTPF1O/wgKNcTl3oYgSkn1xiV8DrVM1zgjB8CvMKS39 1129772390
Received: from gumby.localdomain (88-104-199-135.dynamic.dsl.as9105.com
	[88.104.199.135])
	by frontend2.messagingengine.com (Postfix) with ESMTP id 2E5615703BE
	for <freebsd-questions@freebsd.org>;
	Wed, 19 Oct 2005 21:39:49 -0400 (EDT)
From: RW <list-freebsd-2004@morbius.sent.com>
To: freebsd-questions@freebsd.org
Date: Thu, 20 Oct 2005 02:39:28 +0100
User-Agent: KMail/1.8.2
References: <4356D354.5020509@childeric.freeserve.co.uk>
In-Reply-To: <4356D354.5020509@childeric.freeserve.co.uk>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200510200239.30500.list-freebsd-2004@morbius.sent.com>
Subject: Re: [Fwd: Re: port config questions]
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2005 01:39:54 -0000

On Thursday 20 October 2005 00:14, Chris wrote:
> Sorry, sent to respondent instead of list, resending to list
> Michael C. Shultz wrote:
> > Setting BATCH=YES in /etc/make.conf will prevent those blue screens from
> > popping up.  I'm not sure if this is risky or not but BATCH=YES is a
> > permament fixture in my make.conf and haven't noticed any problems yet.
>
> Does that stop interactive ports being compiled or make them compile
> with defaults? bsd.ports.mk says that BATCH mode would make portupgrade
> 'skip all the important targets' but I'm not sure what that means.

Setting BATCH stops interactive ports being built, many ports also use BATCH 
as an indication that they should run with default settings, or  whatever is 
set in make.conf etc.  A few ports are genuinely interactive, e.g. they may 
have legal conditions that must be  agreed. Many more are conditionally 
interactive, they may set the IS_INTERACTIVE flag if they find inconsistent, 
or incomplete, configuration.

It would be nice if there were some way of running "make config-conditional" 
in just the ports that are out of date. The blue menu screens are a useful 
way of spotting new port options, and you lose that if you set BATCH.