[Gdal-dev] Python next-gen bindings enabled in trunk

[Matt Wilkie]

>> I agree.  I think python scripts should be installed by the makefile,
>> not setup.py, and should end up whereever the other utility programs
>> are installed.

This sounds like a time to request a new "gdal-commands" or "gdal-help" 
comnand. I frequently need to refresh my memory about what gdal 
utilities are available or how to spell them ("now is that gdalwarp or 
gdal_warp?")

Right now with all gdal utils installed in bin I accomplish this with 
"dir %gdal%\bin\*.exe %gdal%\bin\*.py" in a batch file (see below). It's 
not pretty, but functional. This won't work if the utilities end up 
somewhere else with a lot of other unrelated tools. However I wouldn't 
want to force people to add a special directory tree and lengthen the 
PATH just for gdal if that is not inline with the system's standards. 
Having a gdal-help command would make this a non issue (and cross platform).


----- gdal-help.bat -----
@echo off
echo.
echo	Available gdal utilities are:
echo.
if [%GDAL_DATA%]==[] goto :NoGDAL

dir /w %GDAL_DATA%\..\bin\*.exe %GDAL_DATA%\..\bin\*.py
goto :EOF

:NoGDAL
echo	ERROR: gdal environment not set
echo.
------------------------


Ticket #1925 (new enhancement)
create a bew 'gdal-help' or 'gdal-commands' command
http://trac.osgeo.org/gdal/ticket/1925


-- 
matt wilkie
--------------------------------------------
Geographic Information,
Information Management and Technology,
Yukon Department of Environment
10 Burns Road * Whitehorse, Yukon * Y1A 4Y9
867-667-8133 Tel * 867-393-7003 Fax
http://environmentyukon.gov.yk.ca/geomatics/
--------------------------------------------