Date: Thu, 31 Jul 2008 10:52:53 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Bill Moran <wmoran@potentialtech.com> Cc: Marcin Wisnicki <mwisnicki+freebsd@gmail.com>, freebsd-ports@freebsd.org Subject: Re: Problems with portupgrade && xscreensaver-gnome Message-ID: <4891FBF5.6080302@FreeBSD.org> In-Reply-To: <20080731081628.cfb49084.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> <48914065.5020901@FreeBSD.org> <20080731081628.cfb49084.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Moran wrote:
> Understood. But keep in mind that this was not an error, it was a
> warning. Perhaps the ports infrastructure doesn't differentiate between
> those two as much as I think.
The use of the make .warning trick is deprecated in the ports tree
precisely because it leads to confusion. In this case the "warning"
was telling you that you had options selected which conflicted, and
the proper course of action for portupgrade was indeed to bail.
Continuing to focus on the semantics isn't really productive.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4891FBF5.6080302>