[winGRASS] GRASS 5.0.0pre3 selected binaries available

[John Huddleston]

I agree with Andreas about the automated building of Grass5.  Then
designate areas to certain individuals to test the binaries; that
way, it splits the workload over the group.  If no changes are 
made then no testing is required.  If the build is not successful,
then no binaries are put out for that day.  The build of Cygwin
itself went along these lines.

John Huddleston 

-----Original Message-----
From: wingrass-admin at grass.itc.it [mailto:wingrass-admin at grass.itc.it]On
Behalf Of Andreas Lange
Sent: Tuesday, January 22, 2002 9:44 AM
To: Markus Neteler
Cc: grass5 developers list; wingrass
Subject: [winGRASS] Re: [GRASS5] GRASS 5.0.0pre3 selected binaries
available
<snip>

Cygwin:
The cygwin version comes without r.in.gdal, because the latest CVS
version did not compile (ld produces stackdump). Had no time to work on
this. nviz did compile, but it does not run (even does not echo any
error message). So it is of no relevance if it is compiled with
pgsql-support.  


I think that we should find some solution for automating all this. I
believe that we should distribute GRASS mainly as binary. We need a tool
to make some sort of "nightly builds" from the CVS tree, maybe once a
week from the CVS snapshot. This would help to speed up the release
cycle without putting another burden on the GRASS developers. 

cu,

Andreas

-- 
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
url: http://mitglied.tripod.de/AndreasLange
mail: Andreas.Lange_at_Rhein-Main.de - A.C.Lange_at_GMX.net