Date: Mon, 21 Nov 2011 17:20:10 GMT From: =?UTF-8?B?0JzQvtC80YfQuNC7INCY0LLQsNC90L7Qsg==?= <momchil@xaxo.eu> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/162721: ports config menu does not show at all neither complains with TERM not listed in termcap Message-ID: <201111211720.pALHKAFH099079@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/162721; it has been noted by GNATS.
From: =?UTF-8?B?0JzQvtC80YfQuNC7INCY0LLQsNC90L7Qsg==?= <momchil@xaxo.eu>
To: Chris Rees <utisoft@gmail.com>
Cc: Momchil Ivanov <momchil@xaxo.eu>,
"bug-followup@freebsd.org" <bug-followup@freebsd.org>
Subject: Re: ports/162721: ports config menu does not show at all neither complains with TERM not listed in termcap
Date: Mon, 21 Nov 2011 17:34:19 +0100
At Mon, 21 Nov 2011 16:15:12 +0000,
Chris Rees wrote:
> This is correct behaviour.
>
> Imagine running make from a script; that's the usual reason there's no
> valid term.
I would expect it to at least say something like:
===> No valid terminal detected, therefore not showing the menu. Please set a valid terminal to see the configuration menu.
===> Options unchanged
in order to be user friendly and possibly something like "make -D SCRIPT" to suppress the first message if needed in scripts (or may be some environment variable is better for this, don't know).
The current state is not intuitive to somebody who doesn't know this, at least I stumbled upon it some minutes ago and was wondering if there were some configuration options for the port. I had to take a look in the Makefile and find out that there are indeed some, so the next question was: why is the menu not showing up. So some notice about this would be surely helpful.
Greetings,
Momchil
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201111211720.pALHKAFH099079>