#1180: g.extension fails on install step when GRASS is launched from source
directory
-------------------------+--------------------------------------------------
Reporter: marisn | Owner: grass-...@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.1
Component: Default | Version: svn-releasebranch64
Keywords: g.extension | Platform: Linux
Cpu: x86-64 |
-------------------------+--------------------------------------------------
Changes (by hamish):
* cc: frankie (added)
* keywords: => g.extension
Comment:
[see also #1178, #854, and less so #620]
on the DebianGIS list frankie wrote:
{{{
I guess you mean
# GRASS dirs
GRASS_HOME = /build/buildd-
grass_6.4.0~rc6+42329-1+b1-i386-7qc3Bn/grass-6.4.0~rc6+42329
RUN_GISBASE = /build/buildd-
grass_6.4.0~rc6+42329-1+b1-i386-7qc3Bn/grass-6.4.0~rc6+42329/dist.i486-pc-
linux-gnu
RUN_GISRC =
${ARCH_DISTDIR}/demolocation/.grassrc${GRASS_VERSION_MAJOR}${GRASS_VERSION_MINOR}
which should be:
GRASS_HOME = /usr/lib/grass64
RUN_GISBASE = /usr/lib/grass64 ?
but what about the other dir?
--
Francesco P. Lovergine
}}}
short answer is that I'm not sure what RUN_GISBASE should be for post-
build includes. FWIW the demolocation is used for building the
documentation which generally needs the command to be run from inside a
valid GRASS environment (`g.command --html-description`).
with respect to where to install new addons on an end user's system
(considering that they may not have sudo rights to put them in to /usr/ or
/usr/local/, or C:\Program Files\), perhaps we could go for
~/.grass6/addons/ or so and then add that to GRASS_ADDON_PATH
automatically (+additionally)? We could recommend that users add
GRASS_ADDON_PATH to their .bashrc or equiv. in a closing message from
g.extension, but it wouldn't always happen.
need to have another look at how the linux R-cran installed packages
register themselves, and maybe press the GRASS_ADDON_ETC into action (a
home for user-installed addon man pages?)
Maybe add a new flag to g.extension that tries sudo for a system
wide install to /usr/local/ or /c/.../msys/... on Windows? (but then
it's really up to the admin to make sure GRASS_ADDON_PATH is set)
Hamish
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1180#comment:2>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
