[GRASS-dev] [GRASS GIS] #891: add a command g.move

[GRASS GIS]

#891: add a command g.move
--------------------------+-------------------------------------------------
  Reporter:  timmie       |       Owner:  grass-dev@…              
      Type:  enhancement  |      Status:  closed                   
  Priority:  normal       |   Milestone:  6.5.0                    
 Component:  Default      |     Version:  unspecified              
Resolution:  wontfix      |    Keywords:  g.move                   
  Platform:  Unspecified  |         Cpu:  Unspecified              
--------------------------+-------------------------------------------------
Changes (by hamish):

  * keywords:  => g.move
  * status:  new => closed
  * resolution:  => wontfix


Comment:

 It's not really about other users on the system (you can't write to
 directories you don't own either, and grass enforces that for mapset
 access even if there is filesystem group write permissions set), it's more
 about safe concurrent use. If you had two GRASS sessions running in
 parallel, it wouldn't be very nice if the other one suddenly overwrote a
 map in the one you were working in. The same is true for why starting two
 GRASSes running in the same mapset is disallowed (also in that case a
 change by g.region by the twin session could be damaging).

 so it's about keeping the paperwork in order and goes pull, not push.


 see also the r.pack, r.unpack modules if you need to transfer maps between
 different systems/locations, and g.laptop.sh from Addons:
  http://grasswiki.osgeo.org/wiki/AddOns/GRASS_6#g.laptop.sh


 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/891#comment:4>
GRASS GIS <http://grass.osgeo.org>