Date: Wed, 26 Mar 2008 09:39:10 +0100 From: Matthias Andree <matthias.andree@gmx.de> To: freebsd-ports@freebsd.org, ports@freebsd.org Subject: Re: There is no way to know what port options mean (in general) Message-ID: <20080326083910.GA7983@merlin.emma.line.org> In-Reply-To: <20080326053328.GA29448@duncan.reilly.home> References: <20080326053328.GA29448@duncan.reilly.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 26 Mar 2008, Andrew Reilly wrote:
> Suggestion: In lieu of interactive F1 or ? keys popping
> up descriptive windows (which could be nice), it would be
> keen if ports could grow a new target with a name like
> "desc-config" that would print out a paragraph (supplied by
> the port creator/maintainer) that had at least a(n) (explicit)
> reference to the port that the config knob pulled in as a
> dependency. Better would be a short paragraph about why one
> might want to do that, and perhaps what alternatives might
> exist.
>
> Thoughts: ?
Twofold:
1 - descriptions don't hurt
2 - OPTIONS interdependencies are something else, and something which
goes much in the direction of Linux's "make
config/xconfig/gconfig/menuconfig" kconf framework
--
Matthias Andree
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080326083910.GA7983>