>>>> [ Apologies if this ground is well-trodden. Pointers welcome. ] >>>> >>>> For those of us who are used to NFS-based access to parent gates, how >>>> will things like parent proto areas work? Will there be some way for >>>> one to have a parent of ssh://mumble.eng//foo-gate but clue ws(1) in >>>> that /net/xyz.eng/export/ws/foo-gate/proto has populated proto areas >>>> for use when building? >>> >>> In that case, you'll need to specify an nfs path to the parent. You can >>> do this and still use an ssh path for BRINGOVER_WS, and everything should >>> work. >> >> I've never heard of BRINGOVER_WS outside of nightly. Pointers to more on >> how to configure this in the context of ws? > > Sorry, I was answering a different, specific instance of the general > question you asked. > > For ws, nightly, and anything that references the parent workspace > directly, ie not via nfs, you may (and should) specify an nfs path to the > parent.
that should read "ie not via SCM" > For nightly, that can be done via PARENT_WS, regardless of mercurial > settings. > > For ws, that must be done by actually setting your default path via "hg > reparent." Because the .hg/org.opensolaris.protodefs is a generated > script, you may change your default path at any time, and the next > invocation os "ws" will get it right. > > --Mark > > _______________________________________________ > scm-migration-dev mailing list > scm-migration-dev at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/scm-migration-dev >
