| 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 |
Date Of Receipt: 26-AUG-1996 15:16:12.03 From: FLUME::jmf "Joshua M. Friedman Digital UNIX" To: dcj@DEC:.zko.flume CC: odehelp tresvik Subj: Re: Help making a shared sandbox [for mls+] Dave, this just a clarification; you indicate the mlsplus rcs pool is on maniac; my understanding was that the mlsptos pool and future mls* pools were going to share the rcs pool resources with the base os. Is this another pool that you're talking about? The only way I know of to have differently linked files come from different rcs pools is to use the "mksb -subtree" functionality, which requires each link have a distinct set of directories with a clear priority for overlapping directories. You may or may not get this to work in this case. Please investigate this ode capability; it also involves the rc_files/projects file and multiple links/rc files: link1, link2, rc_files1, rc_files2. -josh ----------- Date: Mon, 26 Aug 1996 15:01:39 -0400 From: David Jedlinsky USG <[email protected]> To: [email protected] Cc: [email protected] Subject: Help making a shared sandbox Hi. I'm trying to create a shared sandbox backed by the ase12os pool. This pool appears to be backed by both ase11os.bl3 (link) and goldminos.bl5 (link_os). I would like to create a tree backed by ase12os (link) and mlsplus (link_os), and populate it with symlinks. The problem is that the ase12os rcs tree is on buffer.zk3.dec.com, while the mlsplus rcs tree is on maniac.zk3.dec.com. How do I go about this task (is it possible?), and ensure that when I check out a file that comes from the link_os tree, that I get it from mlsplus, and not goldminos.bl5? The check_out_config should be sufficient, as long as I can find a way to get to both rcs_hosts. Thanks. -Dave Jedlinsky MLS+ Release Engineering [email protected]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2510.1 | Re: Help making a shared sandbox [for mls+] | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Aug 26 1996 17:17 | 27 |
Date Of Receipt: 26-AUG-1996 15:37:19.60 From: KAMLIA::dcj "David Jedlinsky USG" To: jmf@DEC:.zko.kamlia CC: odehelp@DEC:.zko.kamlia, tresvik@DEC:.zko.kamlia Subj: Re: Help making a shared sandbox [for mls+] >Dave, this just a clarification; you indicate the mlsplus rcs pool is >on maniac; my understanding was that the mlsptos pool and future mls* >pools were going to share the rcs pool resources with the base os. Is >this another pool that you're talking about? Yes. The mlsplus pool I'm referring to is our old, sterling-based pool. The rcs trees are completely separate from those in ZKO, due to the history of the MLS+ group (being in Littleton). >The only way I know of to have differently linked files come from >different rcs pools is to use the "mksb -subtree" functionality, which >requires each link have a distinct set of directories with a clear >priority for overlapping directories. You may or may not get this to >work in this case. Please investigate this ode capability; it also >involves the rc_files/projects file and multiple links/rc files: >link1, link2, rc_files1, rc_files2. I will investigate this, thanks for the pointer. -Dave | |||||