From owner-freebsd-ports@FreeBSD.ORG Thu Jun 8 22:07:29 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6406516A503 for ; Thu, 8 Jun 2006 22:07:29 +0000 (UTC) (envelope-from allbery@ece.cmu.edu) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 142B243D46 for ; Thu, 8 Jun 2006 22:07:28 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from [10.9.204.128] (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id 5F29533; Thu, 8 Jun 2006 17:36:49 -0400 (EDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: "Brandon S. Allbery KF8NH" Date: Thu, 8 Jun 2006 17:36:44 -0400 To: Garance A Drosihn X-Mailer: Apple Mail (2.750) Cc: Matthias Andree , freebsd ports Subject: Re: Long-standing portupgrade vs. make config issue 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: Thu, 08 Jun 2006 22:07:29 -0000 On Jun 8, 2006, at 12:35 , Garance A Drosihn wrote: > At 1:58 PM +0200 6/8/06, Matthias Andree wrote: >> >> If I am updating (or installing) a port with portupgrade, the OPTIONS >> ("make config") are prompted twice, once before configuring the port, >> and once when about to install it. >> >> Anyone else observed ... this? > > I have never been prompted twice for a given set of > options. I do, at times, get prompted for the options > of one port, answer that screen and walk away, only to > later see that I was also prompted for the options of > some other port. I have seen something like this but it's not what you think it is. What happens is that portupgrade recognizes some port needs to be installed, and schedules it --- then some other port which needs it installs/upgrades it as a dependency. this also leads to portupgrade failing in the case of a new port because it tries to install it when it's already been installed (I work around with FORCE_PKG_REGISTER=1) -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH