[GRASS-user] error with r.pack addon

Hello,
running the r.pack addon I got the follwoing error:

GRASS 6.5.svn (Spearfish60):/usr/local/src/grass-addons/raster/r.pack >
./r.pack
sh: r.pack: not found
Traceback (most recent call last):
  File "/usr/local/grass-6.5.svn/etc/wxpython/gui_modules/menuform.py",
line 1891, in <module>
    GrassGUIApp( grassTask( sys.argv[1] ) ).MainLoop()
  File "/usr/local/grass-6.5.svn/etc/wxpython/gui_modules/menuform.py",
line 313, in __init__
    processTask(tree =
etree.fromstring(getInterfaceDescription(grassModule)),
  File "/usr/local/grass-6.5.svn/etc/wxpython/gui_modules/menuform.py",
line 1691, in getInterfaceDescription
    raise IOError, _("Unable to fetch interface description for command
'%s'.") % cmd
IOError

What could be the cause for this?

Furthermore, would it be feasible to add such a pack command for all
data types (raster, vector, 3D, data bases) to the GRASS main code?
It's very useful when exchanging result files for remote helping or
interchange.

Thanks and regards,
Timmie

Tim Michelsen wrote:

running the r.pack addon I got the follwoing error:

GRASS 6.5.svn
(Spearfish60):/usr/local/src/grass-addons/raster/r.pack

./r.pack
sh: r.pack: not found

is the script somewhere in the $PATH?

e.g. put it or symlink it into $GRASS_ADDON_PATH. see 'g.manual variables'

Furthermore, would it be feasible to add such a pack command for all
data types (raster, vector, 3D, data bases) to the GRASS main code?
It's very useful when exchanging result files for remote helping or
interchange.

maybe for grass7 once we get the raster format reordered.

for vectors you can just copy the map's directory, for databases "it depends", for DBF easy, for other's you need to g.copy into a fresh
mapset and check db links are relative paths not hardcoded paths.

for now the recommended way is to create a new mapset, g.copy in the
maps you want to transfer, and then package that up with the PERMANENT
mapset into a tarball or zip file.

Hamish

> ./r.pack
> sh: r.pack: not found

is the script somewhere in the $PATH?

no. I executed it from the directory where it is stored within.

Tim:

> > ./r.pack
> > sh: r.pack: not found

Hamish:

> is the script somewhere in the $PATH?

Tim:

no. I executed it from the directory where it is stored within.

It needs to be in the $PATH.

in the msys shell try:
  export PATH="$PATH:"

at the dos prompt I think the current dir is in the %PATH% by default.

but easiest IMO is to put in in GRASS_ADDON_PATH (or symlink acopy of it to there).

Hamish