[GRASS-dev] man/Makefile -> include/Make/Man.make ?

[Glynn Clements]

Markus Neteler wrote:

> >> Could  man/Makefile
> >> be rewritten to include/Make/Man.make
> >> ?
> >
> > What would be the point? The point of including *.make files is that
> > you can have a common set of rules which are included in multiple
> > Makefiles. Given that only man/Makefile would be using those rules,
> > they may as well go into man/Makefile directly.
> 
> The point is that for a "make install" target (main, addons) the MAN
> page needs to be generated immediately like the HTML file, not in
> a global loop.

That's already the case in 7.0. man/Makefile will typically only build
the manpages for the indices; all of the module manpages should
already have been built by that point.

[The original reason for the change was so that any error in
generating the manpage would occur while making the module in
question.]

I'm not contesting the desirability of an "install" target, just the
need for a Man.make file (7.0 has the rules in Html.make, as this is
already included by anything which has HTML documentation from which
the manpage could be built).

-- 
Glynn Clements <glynn at gclements.plus.com>