[GRASS5] Unofficial Grass 5.0.2 for Debian Woody available

[Glynn Clements]

Paul Kelly wrote:

> > (that did not worked with pg 7.3) and splitting documentation in
> > separate package).
> 
> I noticed on the debian web site that someone had commented about putting
> the GRASS man pages in a standard system directory so they could be read
> from the command line with the man command. I don't think this is right as
> they are supposed to be read within GRASS with the g.manual command. I
> don't know what the official policy on this was and wondered how other
> people read their man pages and does anybody install them in the
> standard system directories?

I keep them under $GISBASE, but add $GISBASE/man to MANPATH, so that
they are readable outside of GRASS. I normally use XEmacs for reading
manpages, and having to use the "man" program (via g.manual) within an
xterm would be a nuisance. The same issue would apply to reading
manpages with Xman etc.

The manpages probably shouldn't be installed in /usr/man or
/usr/local/man. There are so many of them, and some of them have names
which would conflict with existing programs; e.g. GRASS has a
"display" manpage which lists the various d.* commands, but
ImageMagick also has a "display" program with a corresponding manpage.

Similarly, if we were to start installing a full set of libraries
(rather than just libgis and libdatetime), either they should go into
their own directory or they should have a prefix (i.e. libgrass_gis).

Also, for 5.1, it might be worth giving all of the GRASS headers a
prefix directory, i.e.

	#include <grass/gis.h>

The headers themselves could then go into /usr/include/grass without
needing to use any -I switches (cf. the number of queries we get
regarding --with-postgres-includes).

-- 
Glynn Clements <glynn.clements at virgin.net>