My difficulty is with install AdvancedViewshedAnalysis extension using GEM within GRASS 6.4.ORC6
command ‘gem6’ is not recognised
command ‘gem install AdvancedViewshedAnalysis.tar’ produces the following error message
ERROR: Could not find a valid gem ‘AdvancedViewshedAnalysis.tar’ (>= 0) in any repository
I have an older version of GRASS (GRASS 6.3.0). From here the command
‘gem6 -i AdvancedViewshedAnalysis.tar -v’ begins to install and then aborts with the following error message:
ERROR: Compilation failed for these module(s):
/private/tmp/grass.extension.Mngj89/AdvancedViewshedAnalysis/src/raster/r.cva
/private/tmp/grass.extension.Mngj89/AdvancedViewshedAnalysis/src/raster/r.prominence
Run ‘make’ manually in each module’s directory for details.
make: *** [default] Error 1
I’ve now run make in both modules (I think), but I still get the same error message. I also don’t understand why the tar file is recognised from GRASS 6.3 but not 6.4. I’m almost certainly doing something very stupid - any help gratefully received!
for the record, everything in the release branch will be
maintained- best attempts will be made to fix bugs, etc.
Including this one. Right now GEM is not getting any
_new_ development though, so no new features are planned.
stuff not under our control we can't do much about beyond
maintaining backwards-compatibility as best we can.
the correct solution in this case is to fix the last few
bugs in r.viewshed and move that into the main source
tree, making the need for the addon app obsolete..
for the record, everything in the release branch will be
maintained- best attempts will be made to fix bugs, etc.
well, probably I haven't used the right word. I just wanted to note
that the last modification in source code of gem is *2* years old
(expect of minor changes). So it's seems to be not actively developed.
Including this one. Right now GEM is not getting any
_new_ development though, so no new features are planned.
That's new information for me. I was thinking that we are going to use
g.extension instead of gem and to drop gem at the end (already done in
trunk).
> Right now GEM is not getting any _new_ development
> though, so no new features are planned.
Martin:
That's new information for me. I was thinking that we
are going to use g.extension instead of gem
right, but one does not preclude the other.
and to drop gem at the end (already done in trunk).
nothing new about enforcing backwards compatibility for
previously released features. that isn't an issue for
grass7, which is why it could be removed there.
and apparently the maintenance burden for this one is low,
which is good.
> Right now GEM is not getting any _new_ development
> though, so no new features are planned.
Martin:
That's new information for me. I was thinking that we
are going to use g.extension instead of gem
right, but one does not preclude the other.
osp, I am apparently too tired, I overlooked all 'no' in your
sentence. Sorry for the noise. No development of gem is planned.
That's not new information for me at all
