Date: Thu, 31 Jul 2008 00:38:47 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-ports@freebsd.org Subject: Re: Problems with portupgrade && xscreensaver-gnome Message-ID: <20080731003847.3ef71888@gumby.homeunix.com.> In-Reply-To: <20080731001156.131efece@gumby.homeunix.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> <20080731001156.131efece@gumby.homeunix.com.>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 31 Jul 2008 00:11:56 +0100
RW <fbsd06@mlists.homeunix.com> wrote:
> 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
Having said that, of course the warning should go to stderr. The problem
seems to be that portupgrade does a 2>&1
output = `cd #{portdir} && #{shelljoin(*cmdargs)} -V PKGNAME -V IGNORE -V NO_IGNORE 2>&1`.to_a
if output.size != 3
warning_message "Makefile possibly broken: #{origin}:"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080731003847.3ef71888>