[GRASS-dev] GRASS_ADDON_PATH question

[Michael Barton]

Thanks.

William Kyngesbury also let me know about this. I'm going to propose a more
generic solution to the problem I'm having.

Michael


On 6/9/07 10:11 AM, "Glynn Clements" <glynn at gclements.plus.com> wrote:

> 
> Michael Barton wrote:
> 
>> From reading the docs, it appears that if you set the GRASS_ADDON_PATH
>> variable, you should have access to any modules or scripts stored therein by
>> simply typing the name of the module or script. However, it doesn¹t seem to
>> work.
>> 
>> I¹ve tried setting this from the GRASS command line, .grass.bashrc file for
>> testing, and my .grassrc6 file
>> 
>> Nothing seems to work. If I type the name of a script residing in the
>> directory I¹ve set in GRASS_ADDON_PATH, I simply get a file not found error.
>> However, if I do ls $GRASS_ADDON_PATH, I get a valid listing of the
>> directory specified.
>> 
>> What am I missing here?
> 
> If it is set, Init.sh adds $GRASS_ADDON_PATH to $PATH. IOW, to be of
> any use, it must be set prior to starting GRASS. Changing it once
> GRASS has started has no effect.
> 
> Note that the contents of ~/.grass.bashrc are read by the session
> shell which is spawned from Init.sh; it will not affect the operation
> of Init.sh itself.

__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton