Hamish wrote: > > > IOW, GRASS_ADDON_PATH is supposed to be the > > > root of the add-on hierarchy, analogous to > > > GISBASE for the main installation. > > no it is not supposed to be like that! > > the fact that it has been used like that in trunk > is a mistake I hope to remedy. > > mainly by having trunk look for GRASS_ADDON_BASE > instead of GRASS_ADDON_PATH if it is actually > wanting --prefix= instead of $PATH. > > > [in grass6] GRASS_ADDON_PATH is what gets prepended > to the OS's $PATH to look for executables.
That's wrong. > currently > 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. If GRASS_ADDON_PATH is just for executables, how are libraries, manual pages, etc, supposed to be found? -- Glynn Clements <gl...@gclements.plus.com> _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user