mk.conf(5)

[Jukka Ruohonen <jruohonen%iki.fi@localhost>]

Hello.

The mk.conf(5) is one of those manual pages that are systematically behind.
It is generally a nightmare to maintain and the information is duplicated in
bsd.README. Possible solutions:

        (a) Document the MKx and USEx variables in mk.conf(5) instead of
            bsd.README.

        (b) Write a script that parses bsd.README and outputs the
            information to mk.conf; cf. the idea in iic(4).

        (c) Make a mk.conf(5) a generic page that points to the
            corresponding files and related information, maybe with a small
            example.

As I see it, (a) is not probably desirable and (b) is prone to errors.
So I would propose (c). Objections?

- Jukka.