Hi all,
What is the best way to install an “unofficial” GRASS addon i.e. one not-hosted at the official SVN repository?
I just checked “g.extension -d” and AFAIK what you essentially need to do in order to install a “single” extension (i.e. not a toolbox) is to checkout the repository and issue make & make install with the correct arguments. I.e something like this:
make
MODULE_TOPDIR=/usr/lib/grass70
RUN_GISRC=/tmp/tmpXuk4Se
BIN=/checkout_dir/bin
HTMLDIR=/checkout_dir/docs/html
RESTDIR=/checkout_dir/docs/rest
MANBASEDIR=/checkout_dir/docs/man
SCRIPTDIR=/checkout_dir/script
STRINGDIR=/checkout_dir
ETC=/checkout_dir/etc
make
MODULE_TOPDIR=/usr/lib/grass70
ARCH_DISTDIR=/checkout_dir
INST_DIR=/home/grassuser/.grass7/addons
install
Is this correct? Are there any caveats that I need to know about?
with kind regards,
Panos
PS, best wishes and a happy new year to everybody 
On Thu, Dec 31, 2015 at 5:59 PM, Panagiotis Mavrogiorgos
<pmav99@gmail.com> wrote:
Hi all,
What is the best way to install an "unofficial" GRASS addon i.e. one
not-hosted at the official SVN repository?
You can specify non-standard repositories in
https://grass.osgeo.org/grass71/manuals/g.extension.html
(note that the version in G7.1 is quite advanced compared to that
included in G7.0.x)
I just checked "g.extension -d" and AFAIK what you essentially need to do in
order to install a "single" extension (i.e. not a toolbox) is to checkout
the repository and issue make & make install with the correct arguments. I.e
something like this:
make \
MODULE_TOPDIR=/usr/lib/grass70 \
RUN_GISRC=/tmp/tmpXuk4Se \
BIN=/checkout_dir/bin \
HTMLDIR=/checkout_dir/docs/html \
RESTDIR=/checkout_dir/docs/rest \
MANBASEDIR=/checkout_dir/docs/man \
SCRIPTDIR=/checkout_dir/script \
STRINGDIR=/checkout_dir \
ETC=/checkout_dir/etc
make \
MODULE_TOPDIR=/usr/lib/grass70 \
ARCH_DISTDIR=/checkout_dir \
INST_DIR=/home/grassuser/.grass7/addons \
install
Is this correct? Are there any caveats that I need to know about?
Looks like overly complicated to me.
This job is essentially done by g.extension.
with kind regards,
Panos
PS, best wishes and a happy new year to everybody
Happy new Year!
Markus
On Sat, Jan 2, 2016 at 1:50 PM, Markus Neteler <neteler@osgeo.org> wrote:
(note that the version in G7.1 is quite advanced compared to that
included in G7.0.x)
Good to know But I am afraid that at least for now I have to stick with
stable versions (i.e. G7.0.x)
> I just checked "g.extension -d" and AFAIK what you essentially need to
do in
> order to install a "single" extension (i.e. not a toolbox) is to checkout
> the repository and issue make & make install with the correct arguments
>
> Is this correct? Are there any caveats that I need to know about?
Looks like overly complicated to me.
This job is essentially done by g.extension.
I agree that this is what g.extension does, but AFAIK g.extension does not
work with non-svn repositories. So my question is if is there anything else
that needs to be done in order to manually install a GRASS extension.
thanks,
Panos
On Jan 3, 2016 10:56 PM, “Panagiotis Mavrogiorgos” <pmav99@gmail.com> wrote:
On Sat, Jan 2, 2016 at 1:50 PM, Markus Neteler <neteler@osgeo.org> wrote:
(note that the version in G7.1 is quite advanced compared to that
included in G7.0.x)
Good to know But I am afraid that at least for now I have to stick with stable versions (i.e. G7.0.x)
That’s fine of course and we’ll find a solution.
I agree that this is what g.extension does, but AFAIK g.extension does not work with non-svn repositories. So my question is if is there anything else that needs to be done in order to manually install a GRASS extension.
Does it need to stay in a remote directory? Or can you have the addon source code locally? The latter is easy to compile and install without any changes needed.
Not sure what your need is.
Markus
On Sun, Jan 3, 2016 at 4:56 PM, Panagiotis Mavrogiorgos <pmav99@gmail.com>
wrote:
On Sat, Jan 2, 2016 at 1:50 PM, Markus Neteler <neteler@osgeo.org> wrote:
(note that the version in G7.1 is quite advanced compared to that
included in G7.0.x)
Good to know But I am afraid that at least for now I have to stick with
stable versions (i.e. G7.0.x)
You can try to download g.extension source code and run it as a script.
It's not guaranteed that it will work but it is worth a try.
https://trac.osgeo.org/grass/browser/grass/trunk/scripts/g.extension
https://trac.osgeo.org/grass/export/67476/grass/trunk/scripts/g.extension/g.extension.py
On Sun, Jan 3, 2016 at 11:46 PM, Markus Neteler <neteler@osgeo.org> wrote:
Does it need to stay in a remote directory? Or can you have the addon source
code locally? The latter is easy to compile and install without any changes
needed.
If you have a local copy of the source code:
cd /path/to/source_of_addon/
make MODULE_TOPDIR=/path/to/compiled_code_of/grass70/
This will compile it.
Markus