There is no way to know what port options mean (in general)

[Matthias Andree]

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