Conference smurf::buildhelp

2533.0. "ODE issue fixed handling duplicate set/sandbox names" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Sep 03 1996 19:21

Date Of Receipt: 	 3-SEP-1996 17:38:33.33
From: 	FLUME::jmf "Joshua M. Friedman Digital UNIX  03-Sep-1996 1736"
To: 	osf_developers@DEC:.zko.flume
CC: 	osf_ode_admins@DEC:.zko.flume, odehelp@DEC:.zko.flume, snow@DEC:.zko.flume,
	tea@DEC:.zko.flume, tresvik@DEC:.zko.flume, decwet::jdaddamio
Subj: 	ODE issue fixed handling duplicate set/sandbox names
Developers who use ODE (DECode-II): 	

This problem/patch is worth noting to all developers; it is part of the
latest released patches to the DECodeII V3.1 tool set and has been
installed and tested in ZK3.  Note each site manages its own patch level.

Up until now, ODE would allow you to do a bco of the same file in more
than one set or sandbox with the same name, either on the same host or
different hosts.  However, this allows an inconsistency to exist, which
causes problems during the bsubmit and can lead to confusion & errors.

Now if you attempt to do this, you will get the following message:

    % bco file
    [ ./path/file ]
    [ ./path/file already checked out to same set in another sandbox;
     branch check-out aborted ]

In this case you either should be using the file in the original
sandbox in which it was checked-out, or you should outdate the work in
the first sandbox (bcs -u -o files), or you should have two different
setnames in use between the two sandboxes if the work really needs to
co-exist.

Thank you, and much thanks to John D'Addamio from the Seattle ODE
development team for addressing this item.

    -Josh Friedman, Digital UNIX Release Engineering

Date Of Receipt: 	 4-SEP-1996 15:32:59.95
From: 	FLUME::jmf "Joshua M. Friedman Digital UNIX"
To: 	glyons@DEC:.zko.flume
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re: ODE issue fixed handling duplicate set/sandbox names

> Josh -
> 
> What is a setname?  If I have 2 different workons going in 2 different 
> sandboxes, can I bco the same file into both of them?
> 
> Thanks.
> 
> Gail Lyons

Gail, if you have a workon session active to different sandboxes,
you can do bco's of the same file, as long as the setname is unique.

If you don't specify a setname with your workon, then the setname equals
the sandbox name.  Once in a workon, currentsb will return the sandboxname
and the full setname (and more stuff with -all).   For example this
command:
	workon -sb mywork
is equivalent to the following, in which the last argument is the setname:
	workon -sb mywork mywork

This will put me in setname Joshua_Friedman_mywork.  This label is used
within RCS for the name of my private branch.  As long as I don't have
a "mywork" sandbox on another machine, or a "mywork" set in another
sandbox, it's ok to bco/bci the same file from multiple sandboxes
independent of one another (until you get multiple versions submitting
to the same pool, then a merge would result).

Hope that helped; please see the documentation for more
(start with http://nsa.zk3.dec.com/rengweb)                    -josh