From owner-freebsd-ports@FreeBSD.ORG Wed Jul 30 23:12:01 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 265C4106566B for ; Wed, 30 Jul 2008 23:12:01 +0000 (UTC) (envelope-from fbsd06+YK=aa2a7b04@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id F237B8FC0A for ; Wed, 30 Jul 2008 23:12:00 +0000 (UTC) (envelope-from fbsd06+YK=aa2a7b04@mlists.homeunix.com) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id F3D6823E49B for ; Wed, 30 Jul 2008 19:11:58 -0400 (EDT) Date: Thu, 31 Jul 2008 00:11:56 +0100 From: RW To: freebsd-ports@freebsd.org Message-ID: <20080731001156.131efece@gumby.homeunix.com.> In-Reply-To: <20080730183307.925ade48.wmoran@potentialtech.com> References: <20080730085123.81542622.wmoran@collaborativefusion.com> <20080730174510.ab0871a3.wmoran@potentialtech.com> <20080730183307.925ade48.wmoran@potentialtech.com> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Problems with portupgrade && xscreensaver-gnome 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: Wed, 30 Jul 2008 23:12:01 -0000 On Wed, 30 Jul 2008 18:33:07 -0400 Bill Moran wrote: > 2) Why is portupgrade dying on a warning message? Why does a poor > decision on one port prevent everything on my system from > upgrading? 3) The error from portupgrade does not immediately point > me to the easy solution, it tricks me into thinking I have to hack > the Makefile. All port build tools make use of "make -V" to read vaiables. With this warning in place, you get something like this: # make -V CONFLICTS "Makefile", line 106: warning: Option KEYRING needs PAM, but PAM is disabled. xscreensaver-[0-9]* xscreensaver-gnome-hacks-[0-9]* which no tool is going to be able to parse. If you just do a "make install", there wont be a problem, so it's understandable that it wasn't spotted.