13 messages in com.perforce.perforce-user[p4] Script for "repository surgery" ...
FromSent OnAttachments
John Hempe01 Jul 2003 16:25 
Stephen Vance01 Jul 2003 20:26 
Carsten Orthbandt02 Jul 2003 00:27 
Paul Goffin02 Jul 2003 01:29 
John Hempe02 Jul 2003 14:03 
Shelley L. Shostak02 Jul 2003 15:00 
Steve Schow02 Jul 2003 15:39 
Moon, Ed02 Jul 2003 18:14 
Robert Cowham03 Jul 2003 02:59 
Hardy, Andrew03 Jul 2003 04:55 
Paul Pharr03 Jul 2003 05:46.py
Steve Schow03 Jul 2003 10:48 
Todd Short03 Jul 2003 12:24 
Subject:[p4] Script for "repository surgery" file renaming.
From:John Hempe (John@metro1.com)
Date:07/02/2003 02:03:15 PM
List:com.perforce.perforce-user

Could you specify exactly _how_ you want to rename your files because parsing the checkpoint isn't exactly rocket science. Carsten Orthbandt

Okay, let me be more specific. I want to change the paths, not the file names
themselves. Let's say I have the following structure: //depot/dirA/file1 //depot/dirB/file2 What I want is to demote dirB under dirA without resetting RCS revision numbers,
because as far as my users are concerned, dirB was always under dirA. So I
want: //depot/dirA/file1 //depot/dirA/dirB/file2 I want to believe it is as simple as taking a checkpoint, replacing all
occurrences of "//depot/dirB" with "//depot/dirA/dirB", move the physical RCS
files from $P4ROOT//depot/dirB to $P4ROOT//depot/dirA/dirB, recovering, and you
are done. Could it be that simple? (Is it?) Even if it is, and I'm not sure it is, the complication to my situation is that
I am using "rcstoperf" to convert my directories. This script leaves an IMPORT
directory structure in the depot which must be maintained as explained in
http://www.perforce.com/perforce/technotes/note031.html. As the note says,
"some Perforce administrators are confused by this", and that includes me in the
context of surgical file re-pathing. --John Hempe