[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
1449.0. "Re: Questions of par.file for ptdx shared sandbox" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Mon May 01 1995 15:42
Date Of Receipt: 1-MAY-1995 14:27:16.33
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: straw@DEC:.zko.flume
CC: odehelp@DEC:.zko.flume
Subj: Re: Questions of par.file for ptdx shared sandbox
Cliff, your assumptions are right about TOOLS_DIR etc.
For BACKING_BUILD, I *stronly* recommend, if possible, that you back
to completed static milestones, i.e. ptdx.bl6, not ptdx.nightly or ptdx.
This allows your work to not break due to new submits. You can control
when you retarget from .bl6 to .bl7, for example, and before hand analyze
the changes from bl6 to bl7 and how they might affect you and if you need
to merge.
A tool called "snaptrack" in your ode-path will do a 3-way diff of
SNAPSHOT files to determine if you have conflicts needing to merge. You
can run snaptrack with no arguments for usage. In your case usage would
be like:
snaptrack /usr/sde/osf1/build/ptdx.bl6/logs/SNAPSHOT \
/usr/sde/osf1/build/ptdx.bl7/logs/SNAPSHOT \
/path/to/your/sharedsandbox/logs/SNAPSHOT
-josh
----------
To: [email protected]
Subject: Questions of par.file
Date: Mon, 01 May 95 14:09:18 -0400
From: "Cliff Straw" <[email protected]>
Josh,
I want to back my shared sandbox by ptdx. What should I use for the
BACKING_BUILD entry in par.file? Do I use the generic
/usr/sde/osf1/build/ptdx or a specific build such as
/usr/sde/osf1/build/ptdx.bl6?
I also assume that I should have the following entries:
TOOLS_DIR=/usr/sde/ode2.0/tools
TOOLS_OPTION=b
DIR_PROT=755
FILE_PROT=644
Cliff
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|