[GRASS-dev] g7 addon scripts not working with trunk due to command syntax/option differences

hi,

all g7 addon scripts which are using e.g. v.to.rast or g.remove are not
working due to command syntax differences.

e.g. in v.to.rast in trunk:

- option 'rows' removed
- instead option 'memory' added

e.g. in g.remove

- g.remove rast=soils (g7) -> g.remove -f type=rast pattern=soils (trunk)

any idea if these syntax differences between g7 and trunk will be backported
at any stage?

if not how to proceed with addon scripts which depend upon some changed
options/syntax?

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/g7-addon-scripts-not-working-with-trunk-due-to-command-syntax-option-differences-tp5164964.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On 30/09/14 13:54, Helmut Kudrnovsky wrote:

hi,

all g7 addon scripts which are using e.g. v.to.rast or g.remove are not
working due to command syntax differences.

e.g. in v.to.rast in trunk:

- option 'rows' removed
- instead option 'memory' added

e.g. in g.remove

- g.remove rast=soils (g7) -> g.remove -f type=rast pattern=soils (trunk)

any idea if these syntax differences between g7 and trunk will be backported
at any stage?

I would plead for a backport to 7.0. These are important syntax changes in much-used modules, so they should, IMHO, be applied before we push out a new major version.

Moritz

On Tue, Sep 30, 2014 at 8:10 AM, Moritz Lennert <
mlennert@club.worldonline.be> wrote:

On 30/09/14 13:54, Helmut Kudrnovsky wrote:

hi,

all g7 addon scripts which are using e.g. v.to.rast or g.remove are not
working due to command syntax differences.

e.g. in v.to.rast in trunk:

- option 'rows' removed
- instead option 'memory' added

e.g. in g.remove

- g.remove rast=soils (g7) -> g.remove -f type=rast pattern=soils (trunk)

any idea if these syntax differences between g7 and trunk will be
backported
at any stage?

I would plead for a backport to 7.0. These are important syntax changes in
much-used modules, so they should, IMHO, be applied before we push out a
new major version.

Sure, they must be backported (before the final release). Now we are at

testing phase. Testing and feedback (very) welcome. See the ticket:

http://trac.osgeo.org/grass/ticket/2414#comment:8

Once we are satisfied and sure that it is what we want, we can backport.
Diff for addons would be great.

There is a page where all changes should be specified:

http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures

Moritz

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

On Tue, Sep 30, 2014 at 10:38 AM, Vaclav Petras <wenzeslaus@gmail.com>
wrote:

On Tue, Sep 30, 2014 at 8:10 AM, Moritz Lennert <
mlennert@club.worldonline.be> wrote:

On 30/09/14 13:54, Helmut Kudrnovsky wrote:

hi,

all g7 addon scripts which are using e.g. v.to.rast or g.remove are not
working due to command syntax differences.

e.g. in v.to.rast in trunk:

- option 'rows' removed
- instead option 'memory' added

e.g. in g.remove

- g.remove rast=soils (g7) -> g.remove -f type=rast pattern=soils (trunk)

any idea if these syntax differences between g7 and trunk will be
backported
at any stage?

I would plead for a backport to 7.0. These are important syntax changes
in much-used modules, so they should, IMHO, be applied before we push out a
new major version.

Sure, they must be backported (before the final release). Now we are at

testing phase. Testing and feedback (very) welcome. See the ticket:

http://trac.osgeo.org/grass/ticket/2414#comment:8

Also related ticket which should be addressed before backporting:
http://trac.osgeo.org/grass/ticket/2437
<http://trac.osgeo.org/grass/ticket/2437#comment:1&gt;

Anna

Once we are satisfied and sure that it is what we want, we can backport.
Diff for addons would be great.

There is a page where all changes should be specified:

http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures

Moritz

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

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