[GRASS-user] Compilation / versions mess up
glynn at gclements.plus.com
Wed May 14 13:55:38 EDT 2008
> > Some months ago I checked out the grass6.3 code using svn.
> > Back then
> > 6.3 was still development. I ended up with a grass_trunk
> > directory and grass63 installed, all happy and fine.
> > Today I went to the grass_trunk dir, issued svn up and
> > compiled &
> > installed grass. To my surprise, I now have grass70 and the
> > old grass63 installed. In order to stay away from the bleeding
> > edge
> > (grass70) and use 6.3, do I need to check out a new grass
> > directory?
> > Or is grass7.0 sort of stable?
I suggest switching to the 6.4 branch. Now that 6.3.0 has been
released, 6.3.x is stable (bug-fixes only), while 6.4.x is the
"normal" development branch (i.e. what the trunk was until recently).
7.x is the "radical development" version, where anything is up for
change. Once development actually starts on 7.x, it may quickly become
incompatible with previous versions of GRASS, and may require some
level of skill to even get it to compile.
> > And how about removing the installed version. I should just
> > delete the
> > /usr/local/grass-7.0.svn directory and the executable in
> > /usr/bin?
> see the "Switch the repository" section here to change over to the dev branch 6:
> but if you've already svn up'd to GRASS 7 I don't know if you can go
> backwards without a fresh checkout.
svn switch https://svn.osgeo.org/grass/grass/branches/develbranch_6
Glynn Clements <glynn at gclements.plus.com>
More information about the grass-user