g.extension.add available to install GRASS Addons SVN modules (GEM replacement)

22 messages Options
Embed this post
Permalink
1 2
Markus Neteler

Re: g.extension.add available to install GRASS Addons SVN modules (GEM replacement)

Reply Threaded More More options
Print post
Permalink
On Thu, Jul 30, 2009 at 11:07 PM, William
Kyngesburye<[hidden email]> wrote:

> On Jul 30, 2009, at 2:59 PM, Markus Neteler wrote:
>
>> Fine with that but the GRASS 7 version currently defines:
>>
>> g.extension -h
>>    prefix   Prefix where to install extension
>>               default: $(HOME)/.grass/addons
>>
>> I guess that this is an oversight and should be
>>               default: $(HOME)/.grass7/addons
>> ?

I'll change to $(HOME)/.grass7/addons is there are no
objections.


>> Additionally: to fully make sense, shouldn't this directory be the default
>> value for the variable
>> GRASS_ADDON_PATH
>>
> GRASS_ADDON_PATH is to a bin folder, and can be multiple paths.  The prefix
> for extension installation should be a single path to a standard bin/lib/etc
> structured folder.

As emerged earlier, it should be outside of the standard GRASS installation.
My point was: if GRASS_ADDON_PATH doesn't point to the g.extension
default, the users will install an extension and then won't find it since it
is not in the path.

>> in
>> lib/init/functions.sh
>> lib/init/grass.py
>> lib/init/init.bat
>>
>> ?


Markus
_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
Martin Landa

Re: g.extension.add available to install GRASS Addons SVN modules (GEM replacement)

Reply Threaded More More options
Print post
Permalink
Hi,

2009/7/30 Markus Neteler <[hidden email]>:

[...]

>> GRASS_ADDON_PATH is to a bin folder, and can be multiple paths.  The prefix
>> for extension installation should be a single path to a standard bin/lib/etc
>> structured folder.
>
> As emerged earlier, it should be outside of the standard GRASS installation.
> My point was: if GRASS_ADDON_PATH doesn't point to the g.extension
> default, the users will install an extension and then won't find it since it
> is not in the path.

probably g.extension could check if given prefix is in
GRASS_ADDON_PATH and update it if needed?

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
1 2