[GRASS-dev] Updated WinGrass packaging re python

2009-12-23 Thread Colin Nielsen
As discussed on a number of tickets (eg. #580), I have updated the NSIS packaging script to separate Python from the main WinGRASS installer. Now, rather than including Python in the package it provides the option of downloading and running the installers for the relevant packages (python,

[GRASS-dev] Re: [GRASS GIS] #843: v.digit broken on new WinGrass release

2009-12-23 Thread GRASS GIS
#843: v.digit broken on new WinGrass release ---+ Reporter: cnielsen | Owner: grass-dev@lists.osgeo.org Type: defect| Status: new Priority: critical |

[GRASS-dev] Re: [GRASS GIS] #788: r.out.gdal and nodata

2009-12-23 Thread Markus Metz
trac server gives problems, doesn't send new comment to list, see https://trac.osgeo.org/grass/ticket/788#comment:7 GRASS GIS wrote: #788: r.out.gdal and nodata --+- Reporter: frankie | Owner:

[GRASS-dev] [GRASS GIS] #845: r.proj[.seg]: new flag to show reprojected bounds and exit

2009-12-23 Thread GRASS GIS
#845: r.proj[.seg]: new flag to show reprojected bounds and exit -+-- Reporter: hamish | Owner: grass-dev@lists.osgeo.org Type: enhancement | Status: new Priority: normal

[GRASS-dev] Re: [GRASS GIS] #788: r.out.gdal and nodata

2009-12-23 Thread GRASS GIS
#788: r.out.gdal and nodata --+- Reporter: frankie | Owner: grass-dev@lists.osgeo.org Type: defect | Status: new Priority: normal | Milestone: 6.4.0

[GRASS-dev] G_message( );

2009-12-23 Thread Hamish
A while back I asked why G_message( ); was used instead of G_message(); (the search terms are too vague to find the original thread) the answer seems to be to hush this compiler warning: main.c:408: warning: zero-length printf format string shrug, H

[GRASS-dev] Re: [GRASS GIS] #845: r.proj[.seg]: new flag to show reprojected bounds and exit

2009-12-23 Thread GRASS GIS
#845: r.proj[.seg]: new flag to show reprojected bounds and exit --+- Reporter: hamish | Owner: grass-dev@lists.osgeo.org Type: enhancement | Status: new Priority: normal

[GRASS-dev] Re: [GRASS GIS] #843: v.digit broken on new WinGrass release

2009-12-23 Thread GRASS GIS
#843: v.digit broken on new WinGrass release ---+ Reporter: cnielsen | Owner: grass-dev@lists.osgeo.org Type: defect| Status: new Priority: critical |

Re: [GRASS-dev] Re: wxPython GUI code base (was Re: a better console and better diff)

2009-12-23 Thread Michael Barton
On Dec 22, 2009, at 8:59 AM, Dylan Beaudette wrote: On Mon, Dec 21, 2009 at 10:43 PM, Hamish hamis...@yahoo.com wrote: Michael wrote: I used wc -l to count lines and files in ./grass65_dev/gui/wxpython (source from develbranch_6) and came up with a considerably larger number. ... lines

[GRASS-dev] Re: [GRASS GIS] #845: r.proj[.seg]: new flag to show reprojected bounds and exit

2009-12-23 Thread GRASS GIS
#845: r.proj[.seg]: new flag to show reprojected bounds and exit --+- Reporter: hamish | Owner: grass-dev@lists.osgeo.org Type: enhancement | Status: new Priority: normal

[GRASS-dev] Re: [GRASS GIS] #845: r.proj[.seg]: new flag to show reprojected bounds and exit

2009-12-23 Thread GRASS GIS
#845: r.proj[.seg]: new flag to show reprojected bounds and exit --+- Reporter: hamish | Owner: grass-dev@lists.osgeo.org Type: enhancement | Status: new Priority: normal

[GRASS-dev] Re: [GRASS GIS] #845: r.proj[.seg]: new flag to show reprojected bounds and exit

2009-12-23 Thread GRASS GIS
#845: r.proj[.seg]: new flag to show reprojected bounds and exit --+- Reporter: hamish | Owner: grass-dev@lists.osgeo.org Type: enhancement | Status: new Priority: normal

[GRASS-dev] Re: [GRASS GIS] #845: r.proj[.seg]: new flag to show reprojected bounds and exit

2009-12-23 Thread GRASS GIS
#845: r.proj[.seg]: new flag to show reprojected bounds and exit --+- Reporter: hamish | Owner: grass-dev@lists.osgeo.org Type: enhancement | Status: new Priority: normal

[GRASS-dev] compiling in OS X 10.6 - possible lib/form problems

2009-12-23 Thread Michael Barton
Hi, I just updated from the svn and almost successfully compiled 6.5. But I get errors in lib/form and related modules. I don't know if this is connected with the issues in ticket https://trac.osgeo.org/grass/ticket/843 or if it is something new. I've still got the same TclTk from

[GRASS-dev] Can Rast_open_* call G_fatal_error()?

2009-12-23 Thread Glynn Clements
I wrote: The fix would be simpler if G_open_cell_old() called G_fatal_error() on errors. This would make life simpler for modules, which currently need to check the return value. Off the top of my head, I don't know of a single case where the caller actually tries to recover from