Re: [GRASS-dev] [GRASS-SVN] r60679 - grass/trunk/lib/python/script

[Martin Landa]

Hi,

2014-06-06 15:49 GMT+02:00 Anna Petrášová :

[...]

> I would suggest to remove the link to GRASS 71 on GRASS website unless
> someone is going to fix this soon.

I have commented out 7.1 [1,2]. I do not believe than someone will fix
it soon. The person who introduced the complete break [3] simply
doesn't care.

Martin

[1] http://grass.osgeo.org/download/software/ms-windows/
[2] http://trac.osgeo.org/osgeo4w/wiki/PackageListing#GRASSGIS
[3] 
http://trac.osgeo.org/grass/changeset/60679/grass/trunk/lib/python/script/core.py

-- 
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-SVN] r60679 - grass/trunk/lib/python/script

[Glynn Clements]

Martin Landa wrote:

> > I would suggest to remove the link to GRASS 71 on GRASS website unless
> > someone is going to fix this soon.
> 
> I have commented out 7.1 [1,2]. I do not believe than someone will fix
> it soon.

Even if they don't, everything except scripts should still work. There
are plenty of projects where daily snapshots are far less reliable,
and where that's considered normal.

On Unix, you'd expect developers to just build from source. But on
Windows, getting a development environment set up is a lot more
effort, so having access to binaries is still useful for developers.

But you're the one hosting them (or not), so it's your call.

> The person who introduced the complete break [3] simply doesn't
> care.

No, that's not true. However, my Windows system is still rather
inadequate as a development platform (it does now have the base
MinGW/MSys installation, but not the libraries required to build
GRASS).

It doesn't absolutely *have* to be me who fixes it. I don't even use
Windows as a development platform for my own purposes. If Windows
script execution never gets implemented, that won't be because a
specific person doesn't care, but because nobody cares.

The changes required to Script.make and/or ScriptRules.make to create
batch files aren't exactly rocket science, but testing them would be
much easier for someone who has a Windows system which can actually
build GRASS.

-- 
Glynn Clements 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-SVN] r60679 - grass/trunk/lib/python/script

[Helmut Kudrnovsky]

>On Unix, you'd expect developers to just build from source. But on
>Windows, getting a development environment set up is a lot more
>effort, so having access to binaries is still useful for developers. 
[...]
>However, my Windows system is still rather
>inadequate as a development platform (it does now have the base
>MinGW/MSys installation, but not the libraries required to build
>GRASS). 

in OSGeo4W [1] there is included a ready-to-use GRASS build environment with
all dependencies [2].

all winGRASS-binaries (OSGeo4W, standalone installers) are based upon this
OSGeo4W build environment.

[1] http://trac.osgeo.org/osgeo4w/
[2] http://trac.osgeo.org/grass/wiki/CompileOnWindows



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Re-GRASS-SVN-r60679-grass-trunk-lib-python-script-tp5143645p5144586.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2284: Keep pressing Ctrl+C in command line

[GRASS GIS]

#2284: Keep pressing Ctrl+C in command line
--+-
  Reporter:  hcho |   Owner:  grass-dev@…  
  Type:  enhancement  |  Status:  reopened 
  Priority:  normal   |   Milestone:  7.0.0
 Component:  Startup  | Version:  svn-trunk
Resolution:   |Keywords:  prompt   
  Platform:  All  | Cpu:  x86-64   
--+-
Changes (by neteler):

  * keywords:  => prompt


Comment:

 I have backported r60216 + r60222 + r60223 to relbr7 in r60735, hopefully
 without side-effects. Please test on Windows + MacOSX.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS 7.0beta3 planning

[Markus Neteler]

Hi,

here a list of backport candidates:

r60692 v.out.ogr
r60674 v.in.ogr
r60656 v.in.ogr
r60596 v.in.ogr
r60595 v.in.ogr
r60662 lib/python/script/raster.py

# needed for QGIS
r60590 include/defs/gis.h, lib/gis/error.c

please comment or backport,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev