[GRASS5] Preparing pre4 source tarball now

Note:
I am preparing the 5.0.0pre4 source tarball now.
Please don't submit to the release branch at time.
I'll send a notification when I'm through.

Thanks,

Markus

Dear GRASS enthusiasts,

GRASS5.0.0pre4 is released. The source code tarball is available
now:
  http://grass.itc.it/grass5/source/

The related NEWS are also available:
  http://grass.itc.it/grass5/source/NEWS.html

Now we need volunteers to build the various binary releases.
Those people may follow the compile rules as described in
documents/release_rules.txt
(especially in terms of PostgreSQL and GDAL support which
is all described there). Above tarball should be used to
prepare a binary release.

Many, many thanks to all contributors who did a great job to
stabilize the current version. I am sure that we are close
to the stable release now.

In case of bugs found in this new release, please report them here:
  http://grass.itc.it/bugtracking/bugreport.html

Thanks again to all contributors who made this release possible!

Cheers

Markus

I'm simplifying and extending G_{lat,lon,llres}_scan. It disallows
this syntax: -DD:MM:SS.PPPPP. If I'm going to extend it to accepting
DD.FFFFFFFF, why not also extend it to accept negative degrees, as
long as there is no N/S or E/W suffix?

--
-russ nelson http://russnelson.com | Okay, enough is enough!
Crynwr sells support for free software | PGPok | Can we PLEASE all stop
521 Pleasant Valley Rd. | +1 315 268 1925 voice | using insecure Microsoft
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | email products???

Russell Nelson wrote:

Is there any way to short-cut the compile process?

Yes; use "gmake5". This script is installed by "make install";
alternatively you can run the copy in the bin.<arch> directory, but
you must use a full pathname, e.g.

  `pwd`/bin.i586-pc-linux-gnu/gmake5 src/libes/gis

OTOH, there's an alternate build mechanism in the "mk" subdirectory;
see mk/README for (brief) details. This is simpler to understand than
the gmake5 build system.

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