Helmut Kudrnovsky wrote: > at the moment in the NSIS-installer-script there are following options for > the destinations-folders: > [http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_6_4/mswindows/GRASS-Installer.nsi#L28] > > Grass64-Release => RELEASE_GRASS_BASE "GRASS" => c:\GRASS > Grass65-Dev => DEV6_GRASS_BASE "GRASS-6-SVN" => c:\GRASS-6-SVN > Grass7 => DEV7_GRASS_BASE"GRASS-7-SVN" => c:\GRASS-7-SVN > > but there is also the development-line of Grass64-svn, on which all > the last WinGrass-Installers for testing are based. > > for a consistent way of a definition of the destination folder > should there maybe the list be adapted to reflect all > development-lines (and for the update-function of the installer)? > > maybe following options for the destination folder? > > Grass64-Release => c:\GRASS-64 > Grass64-Dev => c:\GRASS-64-SVN > Grass65-Dev => c:\GRASS-65-SVN > Grass7-Dev => c:\GRASS-7-SVN
Grass64-Release => %ProgramFiles%\GRASS-64 Grass64-Dev => %ProgramFiles%\GRASS-64-SVN Grass65-Dev => %ProgramFiles%\GRASS-65-SVN Grass7-Dev => %ProgramFiles%\GRASS-7-SVN We *need* this to work. If GRASS can't handle being installed in %ProgramFiles%, that's a blocker, IMHO. Similarly if it can't handle spaces in GISDBASE. -- Glynn Clements <[email protected]> _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
