Conference smurf::buildhelp

2275.0. " workon needs a script wrapper" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Mon May 13 1996 22:49

Date Of Receipt: 	13-MAY-1996 20:55:26.68
From: 	GURU::kucherov "sergei kucherov  13-May-1996 2046"
To: 	odehelp@dec:.zko.guru
CC: 	kucherov@dec:.zko.guru
Subj: 	"workon" needs a script wrapper

Just FYI.
I'll be using a simple, non-production, alias or script wrapper
around "workon" to prevent myself from having two sets of the same name
in different sandboxes. A production quality script would be nice,
if you're bored or would like practice doing something simple with ksh
or perl. Folks would use it too. The ODE maintainers think that the
current situation is fine since it's documented as being broken.
Thus it's up to you, or to each individual, to implement a workon wrapper.

My current idea is for "workon xx" within a sandbox to translate
to ".../workon sandoxname_xx". The user will be insulated somewhat
from the sandbox prefix to the set name. Also, "workon xx" from outside
a sandbox should fail (ie. -sb option should be required).
All options should be passed along to the "real" workon.
This stuff will make it real hard for naive ODE users to hurt themselves,
and should save you many consultations over the long run.

Eventually, I'll implement the above, but I'm giving the odehelp group
first chance at it for the next few weeks.

	sergei

------- Forwarded Message

Return-Path: kucherov
Received: by guru.zk3.dec.com; id AA26901; Mon, 13 May 1996 20:32:17 -0400
Message-Id: <[email protected]>
To: [email protected]
Cc: kucherov
Subject: Reminder when porting fixes: ODE set names must be unique across  
sandboxes 
Date: Mon, 13 May 96 20:32:17 -0400
From: kucherov
X-Mts: smtp


Quick exit: stop reading now if you don't backport fixes to the support pools
or were already aware of the implications of the subject line.

- -----------------------------------------------------------------------------

The ODE manual says:
"You cannot give two of your sets the same name within the same project,
even if the sets are in different sandboxes.
... it is recommended that you choose unique set names
across all of your sandboxes"

ODE does not warn you when "workon" creates more than one identical
set name in different sandboxes. Various ODE commands may appear
to be broken (bco, bci, bsubmit) if you operate on the same filename
in sets with the same name in different sandboxes.
Sets are global, not local to a sandbox, though various config files
may give the opposite impression.

The lack of at least a warning from the ODE "workon" command
when creating more than one set with the same name has been
reported as an ODE bug. Here is the URL for the new ODE bug tracking system
(gen-ptt is obsolete): http://www.zso.dec.com/cgi-bin/ode/wwwgnats.pl

One natural convention when backporting a fix to various support pools
is to use one sandbox per pool and a set name to identify the fix
being backported. But to avoid ODE problems you must remember to choose
a different set name in each sandbox to correspond to the fix.

	sergei


------- End of Forwarded Message