[GRASS5] Any policy for local extensions?

[Thierry Laronde]

Hello,

First some context. I try to hide to users most of the "complexity" of
the importation, transformations, cleaning, topology building and so on,
and hence has created 4 scripts aiming to split the work into 4 steps
and asking for user intervention only when necessary (for example to
correct the connection between segments, moving text insertion points
that are too "far" from areas centroids to be automatically associated
with, etc.).

These scripts are adapted by sourcing a resource file that I want to
stand in the Grass data directory.

And the four steps are tracked by touching four empty files (sort of
lock files).

The question is:
- is there any standard location within the Grass database to put this
  local stuff in?

  At first sight, I wanted to put the "lock" files in the .tmp directory
  but, even if this is unlikely, this merge may create problems some day
  (for example if one decides that GRASS will high-handed empty the .tmp
  directory on exit).

  I have after decided to create a "local" directory under the
  $GISDBASE/$LOCATION_NAME/$MAPSET and put my local stuff (both
  resources and temporary files) here.

  I am correct or is there already some policy about this?
-- 
Thierry Laronde (Alceste) <tlaronde at polynum.org>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C