8 messages in com.perforce.perforce-userReorganizing the depot
FromSent OnAttachments
Fred...@mydata.se16 Sep 1998 13:16 
RJac...@symantec.comRJackson16 Sep 1998 16:14 
Fred...@mydata.se17 Sep 1998 01:07 
Rich...@geodesic.com17 Sep 1998 02:11 
Fred...@mydata.se17 Sep 1998 04:17 
Rich...@geodesic.com17 Sep 1998 04:53 
Eric...@Adobe.COM17 Sep 1998 05:30 
Fred...@mydata.se17 Sep 1998 07:16 
Subject:Reorganizing the depot
From:RJac...@symantec.comRJackson (RJac@symantec.comRJackson)
Date:09/16/1998 04:14:52 PM
List:com.perforce.perforce-user

I believe that I read in the Perforce Technotes area that you can checkpoint the database, change the paths in the checkpoint and in the depot itself, and then restore the checkpoint and that should do it all for you. Try that on your test depot and see if it is any easier.

Rusty

Russell C. Jackson CM Manager Symantec Corporation 310-449-4182

Additional contact information: Cellular: 805-551-6082 Pager: 310-232-2422 rcjjmj at gte.net http://home1.gte.net/rcjjmj

------Original Message----- From: Fredric Fredricson <fredric.fredriksson at mydata.se> Sent: Wednesday, September 16, 1998 10:17 PM To: "perforce-user at perforce.com" <perforce-user at perforce.com> Subject: Reorganizing the depot

We have used p4 for more than two years now and the depot is quite large with ~7500 changes and more than 50k files.

The problem we have is that in the beginning we made some not-so-good decisions about the depot organization. (we were only 7 developers at the time with only one product to worry about)

Now with more than 30 users from five different groups the depot organization is kind of awkward and I would like to do something about this.

After examining the metadata and checkpoint files, and some tests (on a copy of the depot) I came to the conclusion that provided that the changes where not too radical it would actually be possible to "rewrite depot history". That is to move groups of files in the depot, modify history, modify views for branches, labels and clients, and modify the have-information to reflect the new paths.

This would work if all changes where made in the parts of the depot path that where specified in the client, branch and label views.

I have written a perl script that does this reorganization (for 97.3): ftp://ftp.mydata.se/pub/p4/p4mv.pl I have tested it and it seems to work.

Is there anybody out there who has tried anything like this? Is there a better way? All I can think of is branching but that leaves me with clobbered name space or without history.

Any advises? (apart from the most obvious: don't).

/Fredric