btw, my current feeling about the ~/.grass$MAJOR/addons$MAJOR.$MINOR.$BUGVER specific path to protect from binary GIS_H incompatibility is that it may be better to create a ~/.grass65/ in addition to ~/.grass64 to keep the two separate.
The main conflict would be if users swap back and forth between 6.4 and 6.5svn. splitting them up avoids that. on the other hand users (and maybe but not always developers) are expected to only use one version of the stable branch at a time, and monotonically increase their stable version. so they could run 'g.extension.refresh.all' or whatever to rebuild all modules.xml registered C modules soon after upgrade and then be up to date. or just g.extension as usual to manually reinstall/refresh a previous build as needed/when needed. 6.5svn users would be expected to take care of themselves, but esentially the same simple upgrade/rebuild path. seems cleaner as the main (only?) ABI conflict is developers going back and forth between 6.4 and 6.5. what do you think? Hamish _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
