William
On 9/23/07 6:22 PM, "William Kyngesburye" <[EMAIL PROTECTED]> wrote: >> >> I'd recommend keeping the xtnmenu.dat file in GRASS_ADDON_ETC >> because that >> is already an existing GRASS environmental variable. >> >> I'd also recommend using GRASS_ADDON_PATH for the same reason. >> Anything >> listed in GRASS_ADDON_PATH will automatically run from the command >> line and >> from in scripts (like the GUI) without an explicit path specification. >> > I don't mean the actual location of xtnmenu.dat would change, just > the env variable used to locate it. Currently we have: > > GRASS_ADDON_PATH - been around a while, should be left as is > GRASS_ADDON_ETC - fairly new addition > > but will probably need soon: > > GRASS_ADDON_HELP > > And with the possibility of use the makefile fragments for building > and installing extensions (I'm close), we will need to know where > scripts/ and lib/ are. > > My suggestion is to have one base for all this: GRASS_XTN_PATH (stil > multiple paths). Then the various places that need them use > subfolders (bin, lib, docs, etc, scripts) from there. > I understand what you are getting at and maybe this is the best way to go. My point was simply that if you add another environmental path variable, you'll have to make some changes (maybe in init.sh and maybe elsewhere) to get an executable mapped to that path variable to actually run from the command line or in a script. This is already done for GRASS_ADDON_PATH. Michael __________________________________________ Michael Barton, Professor of Anthropology Director of Graduate Studies 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 _______________________________________________ grass-dev mailing list [email protected] http://grass.itc.it/mailman/listinfo/grass-dev
