On 23/10/14 09:44, Helmut Kudrnovsky wrote:
Moritz Lennert wrote
On 23/10/14 02:53, Vaclav Petras wrote:
On Wed, Oct 22, 2014 at 8:28 PM, Glynn Clements
<
glynn@.plus
<mailto:
glynn@.plus
>> wrote:
Martin Landa wrote:
> > Given the history of the Python issue I shall not complain about
a missing Unix shell on Windows...
>
> switching to msys shell is easy, just change in env.bat file
>
> REM set GRASS_SH=%OSGEO4W_ROOT%\apps\msys\bin\sh.exe
>
> to
>
> set GRASS_SH=%OSGEO4W_ROOT%\apps\msys\bin\sh.exe
>
> Probably we could add new item to start menu as it's in G6.
Does the Windows installer still contain MSys? If so, why?
I'm afraid we have an issue with what we want. Do we want to remove msys
in favor of native command line or do we want to have msys available
because it is much better then the MS Windows native command line.
I personally don't care much and I prefer whatever works better. (I'm
not using MS Windows, I have the real unix-like command line on my
system.)
For me the whole idea of the last 10 years of work on getting GRASS
usable on Windows was to get rid of the need of *nix emulation. Msys was
the last remnant of that, and if we can get rid of it and make GRASS
into a "real Windows native" than I'm all for it.
Moritz
FWIW I'm in favour for keeping it.
although winGRASS is able to run without it, there are some nice and for
daily life useful gnu tools coming with msys (e.g. grep ...), IMO it
doesn't harm to ship it with winGRASS.
http://sourceforge.net/projects/unxutils/ ?
Moritz
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
