In preliminary tests (GRASS 6.4 svn release branch), this seems to work very well--and in fact considerably better than it does with GRASS 7/trunk at the moment. One of the extensions I test with consistently gives an install target not found error in trunk, but installs fine with 6.4 release branch.
BUT... There remains some kind of weird problem with setting GRASS_ADDON_PATH. By default, GRASS_ADDON_PATH is set to the desktop, followed by the various /Library and ~/Library paths. I can change it in the GRASS terminal and I can change it in the GUI, but if I use $GRASS_ADDON_PATH in g.extension, it STILL puts stuff into desktop (as the first path in $GRASS_ADDON_PATH). Moreover, I the changes made in GRASS_ADDON_PATH in the terminal do not show up when I display settings from the GUI and the changes made in GRASS_ADDON_PATH with the GUI do not show up in the terminal--and neither are registered by g.extension. If I hard code the directory to which I want to install with g.extension, it puts stuff there. But the GRASS_ADDON_PATH is borked up on the Mac. Michael ____________________ C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On Dec 14, 2011, at 11:12 PM, Hamish wrote: > [by the way, I'd love to hear feedback from Mac users about how well > g.extension(.sh) and the wxGUI extension manager performs in the latest > 6.x.svn] > > Michael wrote: >> The way that William had it set is >> that the default locations for addons were defined as >> /Library/GRASS/6.4 or /Library/GRASS/6.5 etc. The system >> and/or user /Library folder is the normal place for >> preferences, plugins, and other such files on a Mac. While >> the Mac is Unix at heart, people don't interact with its OS >> and file system in the same way Linux users do. If there are >> things we want to hide from normal users, then using a >> hidden directory is OK. But for addons, it is better to put >> them in a place where users expect to find them. FWIW, it >> would be better if preferences were in /Library too because >> that's where they are for other software. > > fwiw, wrt the per-user ~/Library dir in Lion getting hidden, see: > http://osxdaily.com/2011/07/22/access-user-library-folder-in-os-x-lion/ > > afaik the system-wide /Library is still world visible. > > > > Hamish _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
