[GRASS-dev] Re: [GRASS GIS] #820: r.in.wms doesn't work in WinGRASS installer distribution

GRASS GIS trac at osgeo.org
Sat Nov 21 04:55:22 EST 2009


#820: r.in.wms doesn't work in WinGRASS installer distribution
---------------------------+------------------------------------------------
  Reporter:  ddalimonte    |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect        |      Status:  new                      
  Priority:  normal        |   Milestone:  6.4.0                    
 Component:  Packaging     |     Version:  svn-releasebranch64      
Resolution:                |    Keywords:  r.in.wms                 
  Platform:  MSWindows XP  |         Cpu:  Unspecified              
---------------------------+------------------------------------------------
Comment (by neteler):

 Replying to [comment:12 hellik]:
 > Replying to [comment:10 hellik]:
 > > Replying to [comment:8 hamish]:
 > > >  * wget can be replaced by curl if it is installed; there's a flag.
 But really we/msys should ship a copy of wget in our windows package.
 (fwiw Mac ships curl not wget)

 Why should we then ship wget if osgeo4w already ships curl?

 > wget can be download as pre-built-binary from the gnuwin32-website and
 integrated in the windows-package

 Since curl is there is looks more reasonable to get that used at this
 point. Apparently the test fails:
 {{{
 # check if we have wget or curl
 if [ ! -x "`which wget`" ] ; then
     if [ ! -x "`which curl`" ] ; then
         g.message -e "Either 'wget' or 'curl' is required, please install
 one first"
         exit 1
     else
         g.message -v "Using CURL for downloading data."
         USE_CURL=1
     fi
 else
     g.message -v "Using WGET for downloading data."
     USE_WGET=1
 fi
 }}}

 Perhaps the which magic is non-functional with Msys?

 Helmut: could you take out the test in the script and just set
 {{{
 USE_CURL=1
 }}}

 to see what happens then?

 Markus

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


More information about the grass-dev mailing list