Conference smurf::buildhelp

2273.0. "i18n steel pools, re:Confused about how private branches can be used" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Sat May 11 1996 03:32

Date Of Receipt: 	10-MAY-1996 23:20:33.51
From: 	HUNCH::jmf "Joshua M. Friedman OSF/UNIX SDE  10-May-1996 2308"
To: 	fountas@zk3.dec.com
CC: 	i18n@DEC:.zko.hunch, hsu@DEC:.zko.hunch, odehelp@DEC:.zko.hunch
Subj: 	i18n steel pools, re:Confused about how private branches can be used

Bill, you have actually found a setup problem in the trees, which I've
just fixed.  However if anyone has done any bco work to date from
i18nsteel* they will need to recover their work as per my last paragraph.

The way that the i18n trees for pt were set up did not use the normal
model for ode shared sandboxes - normally if a pool backs to a "parent"
(as in i18nptos and ptos), they share a common RCS pool, and they are
considered part of the same project.

In fact, in this case, for reasons I don't fully understand, but related 
to the migration of the pools from HGO to ZK3, i18nptos and ptos have
separate unconnected rcs pools, which means that if you're backed to i18nptos
and bco a file not yet submitted to i18nptos, you'll find the file does
not exist.  You will not get the ptos version.  This seemed to be the
functionality desired by the i18n team.  The same applies to the x11 & dx.

When we created the i18nsteelos,x11,dx pools, this desired (but anomalous)
structure was forgotten, and the i18nsteel trees were setup as "normal"
children of the steel trees.

I have "fixed" the three i18nsteel trees so that they will use the i18n
rcs pools, as did the three i18npt trees, and so you should be able to
find your private branches now as you expected.

However, if any developers have already backed to i18nsteel* and done
any bco's, this work would have used the generic rcs pools, and is no
longer accessible in the i18n trees.  This work needs to manually
copied from the base to the i18n rcs trees or can be managed in private
sandboxes.

Thanks for catching this.  I would like to have this structure reviewed;
it's not clear to me that we want to stick with this model necessarily.

					-Josh

------- Forwarded Message

To: odehelp@quarry.zk3.dec.com
Cc: fountas@quarry.zk3.dec.com, alantam@quarry.zk3.dec.com
Subject: Confused about how private branches can be used
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 10 May 96 12:05:20 -0400
From: fountas@quarry.zk3.dec.com
X-Mts: smtp


Hi,

The I18N group recently (last week) obtained i18n submit pools for steel.
Prior to having these pools in place, I performed my work backed against
platinum pools.  I had been informed that bco/bci/bcreate could be performed
against the platinum pools, however no bsubmits would be allowed.  When I
was ready to check my work in, I could 'resb' to the steel versions and 
my branch information would be known and I could check things in.  

Well, today I decided I would try just that. While backed by the i18nptdx
submit tree, I issued a blog -all to verify things were checked in.  They 
were.  Using 'resb', I backed my sandbox using the i18nsteeldx pool.  
Now, when I issue the blog command, I recieve a "No such file or directory"
error.  However, if I more a file that already exists in the backing tree,
the file exists.

The blog fails to show info on the files in my branch, or files that should
already exist. 

Any ideas why ode complains "no such file or directory"?

Is the submit tree set up correctly?

Regards,

- -bill

- -- 
    __________________________________________________________________________
    Bill Fountas                      
    M/S ZKO3-3/Y25                    
    Digital Equipment Corp.           Internet: fountas@zk3.dec.com
    110 Spit Brook Road               Voice:    1-603-881-2134
    Nashua, New Hampshire 03062-2698  FAX:      1-603-881-2257
    DTN:    381-2134                  WWW:      http://www.zk3.dec.com/~fountas
    __________________________________________________________________________



------- End of Forwarded Message