Date: Thu, 31 Jul 2008 00:11:56 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-ports@freebsd.org Subject: Re: Problems with portupgrade && xscreensaver-gnome Message-ID: <20080731001156.131efece@gumby.homeunix.com.> In-Reply-To: <20080730183307.925ade48.wmoran@potentialtech.com> References: <20080730085123.81542622.wmoran@collaborativefusion.com> <g6ql7b$d5g$1@ger.gmane.org> <20080730174510.ab0871a3.wmoran@potentialtech.com> <g6qp8u$pm4$2@ger.gmane.org> <20080730183307.925ade48.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 30 Jul 2008 18:33:07 -0400 Bill Moran <wmoran@potentialtech.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080731001156.131efece>