Markus Neteler schrieb:
While we should concentrate now on getting out 6.3.0 (e.g.,
fixing issues indicated by Helena [1]), it is important
to start planning for a GRASS 7 dev-branch management.
For GRASS 6, we used for quite some time a mixed solution,
with new code stored in the grass6/ repository and linking
old, relevant code from grass[5]/ into it using some link
scripts.
I am not sure if we want the same for grass7/, too.
On the other hand, replicating code is impossible since
it won't be well maintained given our limited resources.
Thoughts also here?
Let's continue to maintain
GRASS 7 ideas collection
http://grass.gdf-hannover.de/wiki/GRASS_7_ideas_collection
Markus
[1] http://grass.itc.it/pipermail/grass-dev/2007-August/032579.html
I'm only a (non frequent) user of grass. But wouldn't it be nice to have
grass7 with its own shell, to get rid of all these bash dependencies
which make many modules hardly portable (I would prefer a python like
shell).
It is just a suggestion as I'm not able to contribute code.
regards
wolfgang
_______________________________________________
grass-dev mailing list
[email protected]
http://grass.itc.it/mailman/listinfo/grass-dev
