[GRASS-user] AddOn or Script when compiling GRASS from source

[Martin Landa]

Hi,

2011/10/14 Martin Landa <landa.martin at gmail.com>:
>>> g.extension creates symlinks to ameliorate the
>>> misuse. FYI I plan to modify g.extension in grass6
>>> to install executables to the main ADDON dir,
>>> instead of to scripts/ and bin/ + symlinks back to
>>> the main dir. The current way is needlessly
>>> complicated.
>>
>> There should only need to be a single environment variable, from which
>> all components of add-ons (executables, libraries, data files,
>> documentation) should be able to be found.
>
> that's how it's working in G7.
>
>> If GRASS_ADDON_PATH is just for executables, how are libraries, manual
>> pages, etc, supposed to be found?
>
> It requires other variables like GRASS_ADDON_ETC, GRASS_ADDON_LIB, it
> was a main reason why I changed it in G7. AFAIU Hamish would like to
> define in G7 two variables, GRASS_ADDON_BASE (g.extension) and
> GRASS_ADDON_PATH eg. for user scripts (?)

so what's the preferred solution for G7

1) single variable GRASS_ADDON_PATH for all components (as it is)
2) two variables - GRASS_ADDON_BASE and GRASS_ADDON_PATH (path only as in G6)

?

Martin

-- 
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa