2011/12/15 Michael Barton <michael.bar...@asu.edu>: >> it doesn't work to put GRASS_ADDON_PATH into .grass.bashrc, >> you need to export it from your ~/.bashrc or ~/.profile. >> (and it is too invasive to start appending to those automatically) > > It is not good to mess with these on the Mac unless you know what you are > doing. That rules out most Mac users.
well, not only Mac-users ;-) >> it needs to be set before init.sh/grass.py gets run. >> >> my plan for trunk was to rename GRASS_ADDON_PATH (taken over >> by g.extension.py) to GRASS_ADDON_BASE, then re-add >> GRASS_ADDON_PATH as a $PATH component, if it exists. if it was >> not already set then nothing is added to the environment.. it's >> there if you want to use it, and not if you don't. >> >> that does not preclude the wxGUI having a Preference setting >> to add some dirs to the copy of the $PATH it maintains, starting >> with any existing GRASS_ADDON_PATH enviro variable that was >> there when it launched. > > All this is fine. However, GRASS_ADDON_BASE should not be a hidden file on a > Mac. It is problem enough that preferences are there if you ever have to mess > with them outside of the GRASS GUI. There is no GRASS_ADDON_BASE. Anyway it should be controlled only by `g.extension` (user scripts can live somewhere else). So basically there is no problem that g.extension installs extensions to the hidden directory. Martin -- Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev