[GRASS-dev] g.extension.add available to install GRASS Addons SVN modules (GEM replacement)

Markus Neteler neteler at osgeo.org
Thu Jul 30 17:39:07 EDT 2009


On Thu, Jul 30, 2009 at 11:07 PM, William
Kyngesburye<woklist at kyngchaos.com> 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


More information about the grass-dev mailing list