>One Windows problem is that there is no package manager >who takes the user's hand which is the reason for these large >standalone applications on MS Windows. [...] >> >> Personally, I am a bit afraid that by going down the first route we >> concentrate much developer time that could be spent on other (IMHO more >> useful) things and we also risk to make GRASS less efficient for those >> that >> have taken the time to pass the hurdle. > >Changing the installer to take care of a system-wide Python >installation that also resolves conflicts is probably far more work >than to use the existing mechanism of GRASS6.
I support this. this kind of installer opens a Pandora's box (e.g. how to solve problems if another software installs another system-wide incompatible python, ...), than it helps. >> In other words, there are some types of users (those that don't read >> anything provided by the developers) for whom I am sometimes tempted to >> just >> say "RTFM" instead of trying to find ways to make it possible for them to >> still use GRASS. at least in the winGRASS-standalone installer we offers an option to open the manuals/first time user pages if the installer quits. ----- best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Re-GRASS-PSC-too-many-branches-retirement-GRASS6-5-svn-develbranch6-tp5133400p5134122.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
