Ohhh!
This indeed makes sense. We still need a vista version. But the less
duplication the better.
Michael
On Apr 2, 2009, at 1:10 PM, Moritz Lennert wrote:
On 02/04/09 18:51, Michael Barton wrote:
Thanks. This is good to know. Of course the user/lab manager still
needs to create a *.bat file from instructions in a blog (at least
now referenced on the WIKI).
No, what I meant is that with the osgeo4w installation environment,
someone could package a stand-alone GRASS installer and make it
available via the GRASS web site. Seems more sustainable to me than
having separate efforts going into a stand-alone installer and
osgeo4w. I guess someone would have to try the osgeo4w path to an
installer once to see how user and lab-friendly this really is.
Moritz
Michael
______________________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
On Apr 2, 2009, at 2:06 AM, Moritz Lennert wrote:
On 31/03/09 06:58, Martin Landa wrote:
Hi,
2009/3/31 Michael Barton <[email protected]>:
Native, stand alone installer for GRASS should be a high
priority. I guess
we need both an XP and Vista version.
personally I have no problem with osgeo4w installer. Ideally
should be
mentained both - standalone and osgeo4w - if we have enough
manpower.
If no, I would incline to osgeo4w.
I can only repeat that the two are not opposed, but that you can
create a standalone installer on the basis of osgeo4w:
http://trac.osgeo.org/osgeo4w/wiki/FAQ#HowdoIperformanofflineorcomputerlabinstall
AFAICT, you just need to create the .bat file mentioned in the
QGIS blog and you have a clickable installer.
Moritz
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
