Conference smurf::buildhelp

1061.0. "more, re: changing the name of a sandbox" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Tue Nov 08 1994 16:37

Date Of Receipt: 	 8-NOV-1994 16:06:03.20
From: 	FLAMBE::jmf "Joshua M. Friedman OSF/UNIX SDE  08-Nov-1994 1603"
To: 	schloss@DEC:.zko.flambe
CC: 	odehelp@DEC:.zko.flambe
Subj: 	more, re: changing the name of a sandbox

Mike, in Jim's mail (attached) he points out some items, but there's a
big issue that was missed.  Jim stated:
> 3.  Finally, the src/.BCS-.... files, if you have them, will have the
> default set name as part of their name.  You don't want these to get
> lost either.

If you have checked any files out, you'll have a file called:
    .BCSset-Michael_Schloss_sandbox
If you've done any bci's you'll also have a .BCSlog-... file.
You can't just rename these files and proceed to use the files, because
internally, RCS uses the symbolic name Michael_Schloss_sandbox.  Changing
the sandbox name will make all the already bco'd file no longer accessible
from within the sandbox without a series of new bco's or bmerge's.

I'm confused: are you really changing the name of a sandbox, i.e. from
	workon -sb sandbox
to
	workon -sb sb

or are you moving a sandbox (eg called "foo") from sandbox/foo to sb/foo?
If this is what you're doing, then the sandbox name isn't changing, and
the issues about the RCS symbol and the .BCS files don't exist.

-josh


------- Forwarded Messages

Return-Path: schloss 
Delivery-Date: Mon, 07 Nov 94 15:14:35 -0500
Return-Path: schloss
Received: from styrax.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/30Mar94-0502PM)
	id AA22912; Mon, 7 Nov 1994 15:14:30 -0500
Received: from localhost by alpha.zk3.dec.com; (5.65/1.1.8.2/15Sep94-0303PM)
	id AA06448; Mon, 7 Nov 1994 15:14:06 -0500
Message-Id: <[email protected]>
To: odehelp
Subject: changing the name of a sandbox
Date: Mon, 07 Nov 94 15:14:05 -0500
From: schloss
X-Mts: smtp

I would like to change the name of an existing sandbox,
say from "sandbox" to "sb".  Is this doable?  Does it
require more than mvdir and editing ~/.sandboxrc?

Mike Schloss


------- Message 2

Return-Path: [email protected] 
Delivery-Date: Mon, 07 Nov 94 16:06:53 -0500
Return-Path: [email protected]
Received: from flume.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/30Mar94-0502PM)
	id AA27770; Mon, 7 Nov 1994 16:06:50 -0500
Received: by flume.zk3.dec.com; (5.65/1.1.8.2/23May94-1035AM)
	id AA16753; Mon, 7 Nov 1994 16:06:28 -0500
Date: Mon, 7 Nov 1994 16:06:28 -0500
From: Jim McGinness <[email protected]>
Message-Id: <[email protected]>
To: [email protected]
Subject: Re:  changing the name of a sandbox
Cc: [email protected]

Yes you need to do more than mvdir and edit .sandboxrc.

1.  You need to edit the rc_files/shared file on the line where it
says "sandbox_base".

2.  There is the rc_files/sets file which has the sandbox location
embedded in the name of the default set.

3.  Finally, the src/.BCS-.... files, if you have them, will have the
default set name as part of their name.  You don't want these to get
lost either.

4.  The .BCSlock file contains the name of the sandbox directory, too,
so you might as well fix it while you're at it.  I just don't know of
any place where the directory name here gets used.

	-- jmcg


------- End of Forwarded Messages

Date Of Receipt: 	 8-NOV-1994 16:20:07.78
From: 	FLUME::jmcg "Jim McGinness"
To: 	jmf@DEC:.zko.flume
CC: 	odehelp schloss
Subj: 	Re:  more, re: changing the name of a sandbox

Josh is right to point this out.  I was muddling along thinking about
moving a sandbox from one location to another, then noticed the
other places the sandbox name (as opposed to the path prefix of the
sandbox_base) was used and I got carried away.

The sandbox can be moved by just doing step 1.  You have to keep the
sandbox name the same if any files are mentioned in the .BCS-...
files.  The name of the sandbox/set is part of the label embedded in
the RCS file when files have been checked out.

	-- jmcg