>So, there is a vision by some that for the reasons of apparent >"incompatibility" between the way GRASS works and Windows, >GRASS has to >be different on windows. I.e. that GRASS has to become a monolithic >application on Windows.
I wouldn't call it incompatibility and I think GRASS hasn't to be different on windows. I like mounteering, in winter and in summer; it's always climbing, but depending of the season, you need different/other clothes, tools etc ... so maybe windows is some kind of icy winter time ... ;-) >I also think that some of the debate comes from the question of whether >the wxGUI should have a special status or whether it should just be >treated as one of the hundreds of modules that GRASS offers. maybe; but what about the scripts? >And AFAIK, no one has suggested that the GRASS installer should just >install Python system-wide, but rather that a correct Python >installation would be left to the user, with possible help in the >installer (e.g. suggesting installation if it detects no installation at >all, clear documentation on different cases, etc). [...] >There is quite a large margin between creating a monolithic application >with everything bundled and leaving the user alone... what will you suggest to the user, if there is already an system wide python (installed by another software, sometimes adapted to their needs), but incompatible for winGRASS? deinstall/break the other software and install winGRASS? some operating system design flaws comes in here ... which we can't change (... just remember dll-hell :-)) >To answer Martin's call for concrete action: how difficult would it be >for you, Helmut, to create a GRASS installer without Python, so that we >can test that scenario ? I don't have the Windows build toolchain set up >at the moment, but if it's more work for you than a few lines of code to >change and command to create a new package, then I'll try to find the >time to do that. not including python, have a look here: http://trac.osgeo.org/grass/browser/grass/trunk/mswindows/GRASS-Packager.bat.tmpl#L113 @echo Copy Python content to PACKAGE_DIR\Python27 and then maybe you have to adapt the starting script and all other ?! is having a starting script monolithic or non-monolithic? ;-) and if you want winGRASS operating really from everywhere in windows, you have to add entries accordingly to the windows registry. ----- best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Handling-of-Python-scripts-on-MS-Windows-tp5081335p5134852.html Sent from the Grass - Dev mailing list archive at Nabble.com. _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
