[GRASS-dev] Re: [GRASS GIS] #1178: WinGrass: g.extension - problem with path to $GISBASE

GRASS GIS trac at osgeo.org
Sat Oct 2 15:50:40 EDT 2010


#1178: WinGrass: g.extension - problem with path to $GISBASE
---------------------------------------------------------------+------------
 Reporter:  hellik                                             |       Owner:  grass-dev@…              
     Type:  defect                                             |      Status:  new                      
 Priority:  major                                              |   Milestone:  6.4.1                    
Component:  Installation                                       |     Version:  svn-releasebranch64      
 Keywords:  wingrass, g.extension, path, installation, addons  |    Platform:  MSWindows Vista          
      Cpu:  x86-32                                             |  
---------------------------------------------------------------+------------

Comment(by glynn):

 Replying to [comment:19 hamish]:

 > IIRC the fstab file was one of the MSys dev's "we don't support spaces
 in path names and won't even accept bugfix patches" fun times. (/etc/fstab
 is whitespace delimited)
 >
 > Should we (can we?) rewrite that file each time at program startup to
 reflect the current shortname version of the path?

 It's important to be clear on one thing: are we providing "GRASS for
 Windows" or "GRASS for MSys"? You cannot make one package which does both
 perfectly. Improving MSys compatibility will tend to harm Windows
 compatibility and vice-versa.

 MSys shouldn't be needed at run time other than for shell scripts. If
 these are problematic, maybe we should consider moving to Python for
 6.4.1?

 Building is always going to be problematic. make is fundamentally a Unix
 tool, but using anything else puts a substantial (and arguably
 unreasonable) burden upon developers. Ordinarily you would just assume a
 certain level of competence from people who want to build from source.

 If you want an "easy mode" in the form of g.extension, I think that it's
 primarily g.extension's responsibility to handle the Windows issues.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1178#comment:21>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list