[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

1396.0. "ODE Admin question" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Apr 18 1995 20:21

Date Of Receipt: 	11-APR-1995 13:06:21.86
From: 	SMURF::WASTED::"cdancy@mmsrv.zko.dec.com" "11-Apr-1995 1305"
To: 	odehelp@zk3.dec.com
CC: 	cdancy@mmsrv.zko.dec.com
Subj: 	ODE Admin question

We have two submit trees (shared sandboxes); one backed to the other.
One is for a near term release, and the other for a later release.

When someone does a bcreate and bsubmit to the near term tree, it does
not show up in the later tree, until a mklinks is done in the
later tree.  Is this the case with your trees also?

-Chip Dancy

T.RTitleUserPersonal
Name
DateLines
1396.1Re: ODE Admin questionAOSG::FILTERAutomatic Posting Software - mail to flume::puckTue Apr 18 1995 20:2222
Date Of Receipt: 	11-APR-1995 13:18:11.92
From: 	SMURF::QUARRY::"vandyck@cardinal.zk3.dec.com" "11-Apr-1995 1316"
To: 	"Chip Dancy, Multimedia/Light and Sound Software Group"  <cdancy@mmsrv.zko.dec.com>
CC: 	odehelp@zk3.dec.com
Subj: 	Re: ODE Admin question

Absolutely. There's no automatic connection between the two, only a 
relationship established via the link in the later tree.


	-Grant

| We have two submit trees (shared sandboxes); one backed to the other.
| One is for a near term release, and the other for a later release.
| 
| When someone does a bcreate and bsubmit to the near term tree, it does
| not show up in the later tree, until a mklinks is done in the
| later tree.  Is this the case with your trees also?
| 
| -Chip Dancy


1396.2Re: ODE Admin questionAOSG::FILTERAutomatic Posting Software - mail to flume::puckTue Apr 18 1995 20:2433
Date Of Receipt: 	11-APR-1995 13:34:37.95
From: 	SMURF::WASTED::"cdancy@mmsrv.zko.dec.com" "11-Apr-1995 1333"
To: 	"Grant Van Dyck" <vandyck@cardinal.zk3.dec.com>
CC: 	"Chip Dancy, Multimedia/Light and Sound Software Group"  <cdancy@mmsrv.zko.dec.com>,
	odehelp@zk3.dec.com, cdancy@mmsrv.zko.dec.com
Subj: 	Re: ODE Admin question
Thanks Grant.  One follow-up question: 	

Do you do a mklinks in the later release sandbox on some periodic basis?
Or, is it only done each baselevel?
(Perhaps because your submit trees may be only open for a short time?).

-Chip



<<<Absolutely. There's no automatic connection between the two, only a 
<<<relationship established via the link in the later tree.
<<<
<<<
<<<	-Grant
<<<
<<<| We have two submit trees (shared sandboxes); one backed to the other.
<<<| One is for a near term release, and the other for a later release.
<<<| 
<<<| When someone does a bcreate and bsubmit to the near term tree, it does
<<<| not show up in the later tree, until a mklinks is done in the
<<<| later tree.  Is this the case with your trees also?
<<<| 
<<<| -Chip Dancy
<<<
<<<

1396.3Re: ODE Admin questionAOSG::FILTERAutomatic Posting Software - mail to flume::puckTue Apr 18 1995 20:2552
Date Of Receipt: 	11-APR-1995 13:51:20.47
From: 	SMURF::QUARRY::"vandyck@cardinal.zk3.dec.com" "11-Apr-1995 1350"
To: 	"Chip Dancy, Multimedia/Light and Sound Software Group"  <cdancy@mmsrv.zko.dec.com>
CC: 	"Grant Van Dyck" <vandyck@cardinal.zk3.dec.com>, odehelp@zk3.dec.com
Subj: 	Re: ODE Admin question

Generally we don't back shared sandboxes by other shared sandboxes, they're 
backed by fully populated baselevel tree. For example:

ptos is backed by ptliteos.bl2

when ptliteos produces a stable tested bl3 tree, then a retarget/merge 
operation occurs, where the link is repointed, and any files that changed 
between ptliteos.bl2 and ptliteos.bl3 that also exist as real files in ptos 
get 3-way merged to pick up the diffs.

bco -km -jPTLITEOS_BL2:PTLITEOS_BL3 foo.c   # in a ptos sandbox


	-Grant



| Thanks Grant.  One follow-up question:
| 
| Do you do a mklinks in the later release sandbox on some periodic basis?
| Or, is it only done each baselevel?
| (Perhaps because your submit trees may be only open for a short time?).
| 
| -Chip
| 
| 
| 
| <<<Absolutely. There's no automatic connection between the two, only a 
| <<<relationship established via the link in the later tree.
| <<<
| <<<
| <<<	-Grant
| <<<
| <<<| We have two submit trees (shared sandboxes); one backed to the other.
| <<<| One is for a near term release, and the other for a later release.
| <<<| 
| <<<| When someone does a bcreate and bsubmit to the near term tree, it does
| <<<| not show up in the later tree, until a mklinks is done in the
| <<<| later tree.  Is this the case with your trees also?
| <<<| 
| <<<| -Chip Dancy
| <<<
| <<<
| 


1396.4Re: ODE Admin questionAOSG::FILTERAutomatic Posting Software - mail to flume::puckTue Apr 18 1995 20:3020
Date Of Receipt: 	11-APR-1995 14:29:25.79
From: 	SMURF::WASTED::"cdancy@mmsrv.zko.dec.com" "11-Apr-1995 1427"
To: 	"Grant Van Dyck" <vandyck@cardinal.zk3.dec.com>
CC: 	"Chip Dancy, Multimedia/Light and Sound Software Group"  <cdancy@mmsrv.zko.dec.com>,
	odehelp@zk3.dec.com, cdancy@mmsrv.zko.dec.com
Subj: 	Re: ODE Admin question

Thanks,
When I talked to Sean last week, he gave me the impression that the
submit trees were all backed from one to previous to the previous.  I
probably misunderstood.

However, I know that he told me that changes submitted to the earlier of
two releases, were immediately seen in the submit tree of the later release.

Which type of trees is it that only contain files pertinent to that release and
are linked all the way back to the first OSF release?

-Chip

1396.5Re: ODE Admin questionAOSG::FILTERAutomatic Posting Software - mail to flume::puckTue Apr 18 1995 20:3732
Date Of Receipt: 	11-APR-1995 15:35:55.39
From: 	SMURF::QUARRY::"vandyck@cardinal.zk3.dec.com" "11-Apr-1995 1534"
To: 	"Chip Dancy, Multimedia/Light and Sound Software Group"  <cdancy@mmsrv.zko.dec.com>
CC: 	"Grant Van Dyck" <vandyck@cardinal.zk3.dec.com>, odehelp@zk3.dec.com
Subj: 	Re: ODE Admin question

| Thanks,
| When I talked to Sean last week, he gave me the impression that the
| submit trees were all backed from one to previous to the previous.  I
| probably misunderstood.

No that's not the case.

| 
| However, I know that he told me that changes submitted to the earlier of
| two releases, were immediately seen in the submit tree of the later release.
| 

No that's not correct either.


| Which type of trees is it that only contain files pertinent to that release a
nd
| are linked all the way back to the first OSF release?

That's what a shared sandbox is.



				-Grant