Changes between Version 19 and Version 20 of pkg-grass


Ignore:
Timestamp:
02/22/09 02:26:46 (16 years ago)
Author:
hamish
Comment:

osgeoid url

Legend:

Unmodified
Added
Removed
Modified
  • pkg-grass

    v19 v20  
    4343== Errata ==
    4444
    45  * While the GRASS libraries and modules are typically extremely well tested and stable, this new Windows install package is not. Because we are very confident in the underlying GIS code we hope that any problems due to the new Windows packaging efforts will be superficial and quickly resolved. You can help this process by reporting bugs: if it seems to be the fault of the installer report bugs to the [http://trac.osgeo.org/osgeo4w/report OSGeo4W bug tracker], if it seems to be the fault of GRASS, report bugs to the [http://trac.osgeo.org/grass/report GRASS bug tracker]. You will need to create yourself an [http://trac.osgeo.org/osgeo4w/login OSGeo ID] to submit and comment on bugs. Bugs don't get fixed unless people point them out! It is expected that some issues related to spaces in the path names still exist, but we hope to have found most of these by now. Also it is likely that the wxPython GUI still has some gremlins in it, please help us find and fix them by reporting any errors you come across! Typically once found they are easy to fix.
     45 * While the GRASS libraries and modules are typically extremely well tested and stable, this new Windows install package is not. Because we are very confident in the underlying GIS code we hope that any problems due to the new Windows packaging efforts will be superficial and quickly resolved. You can help this process by reporting bugs: if it seems to be the fault of the installer report bugs to the [http://trac.osgeo.org/osgeo4w/report OSGeo4W bug tracker], if it seems to be the fault of GRASS, report bugs to the [http://trac.osgeo.org/grass/report GRASS bug tracker]. You will need to create yourself an [http://www.osgeo.org/osgeo_userid/ OSGeo ID] to submit and comment on bugs. Bugs don't get fixed unless people point them out! It is expected that some issues related to spaces in the path names still exist, but we hope to have found most of these by now. Also it is likely that the wxPython GUI still has some gremlins in it, please help us find and fix them by reporting any errors you come across! Typically once found they are easy to fix.
    4646
    4747 * If a bunch of errors appear in the DOS command window (e.g. "Traceback ... wxgui.py, line 1234") you can cut and paste these to a text file or bug report by right-clicking on the window and selecting "Mark". Scroll up to the top of the text and drag the highlight box down over the text with the left mouse button. When you are done highlighting right click. You can then Paste the text from the clipboard.