Conference smurf::buildhelp

Date Of Receipt: 	12-JUN-1995 12:31:38.96
From: 	SMURF::QUARRY::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	[email protected], [email protected]
CC: 	
Subj: 	Re:  how to create a "backing tree"?

Mike,

Do you need the *entire* src tree - kernel & commands?  You could do a
big bco loop driven off of the ptos.bl4 SNAPSHOT file (which is saved
off in rcs under ptos/logs/RCS/SNAPSHOT.build from every build).

(Using the bl4 snapshot is equivalent to using the PTOS_BL4 label, and,
in fact, you could use the SNAPSHOT file for just the filenames and
use the checkout label instead of the numbers if you like; they'd be
equivalent.)

This would undoubted take a very long time with 'bco'.

While we don't normally do this, we could temporarily export read-only
the rcs pool from buffer and you could do the same with co instead of
bco - this is what the ode command script 'mkback' does (take a look at
its odeman page and the script).  It would run a *lot* faster this way.

-josh


----------
From [email protected]  Mon Jun 12 10:41:42 1995
Delivery-Date: Mon, 12 Jun 95 10:41:48 -0400
Return-Path: [email protected]
Received: from quarry.zk3.dec.com by flume.zk3.dec.com; (5.65v3.0/1.1.8.2/16Jan95-0946AM)
	id AA06830; Mon, 12 Jun 1995 10:41:42 -0400
Received: from localhost by quarry.zk3.dec.com; (5.65/1.1.8.2/13Feb95-0113PM)
	id AA02841; Mon, 12 Jun 1995 10:41:27 -0400
Message-Id: <[email protected]>
To: [email protected]
Subject: how to create a "backing tree"?
Date: Mon, 12 Jun 95 10:41:27 -0400
From: [email protected]
X-Mts: smtp
Status: R


What would be the easiest way to create a sandbox with
all of the files checked-out (unlocked) that are tagged
with PTOS_BL4?

-mike

Date Of Receipt: 	12-JUN-1995 14:34:42.52
From: 	SMURF::QUARRY::mjr "Michael Rickabaugh USG  12-Jun-1995 1433"
To: 	Joshua M. Friedman OSF/UNIX SDE <jmf@DEC:.zko.quarry>
CC: 	[email protected]
Subj: 	Re: how to create a "backing tree"?

>Do you need the *entire* src tree - kernel & commands?

I would prefer to have access to the entire tree.

A lot of times, I get asked "What baselevel did <something> go
into?"  Sometimes I need to ask the question to myself.  Usually,
this occurs AFTER the normal backing trees get blown away.

It would be great if I could say

	bco -u -rPTOS_BL4 <directory>

and then everything in the directory gets pulled out.

-mike

Date Of Receipt: 	12-JUN-1995 14:58:01.50
From: 	SMURF::QUARRY::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	mjr@DEC:.zko.quarry
CC: 	[email protected]
Subj: 	Re: how to create a "backing tree"?

Mike, Actually you can do effectively what you want.

To get all the files in a directory:

    % workon -sb ... ...
    % cd directory    /* directory should be empty */
    % mklinks -norecurse .
    % bco -u -rPTOS_BL4 *

The only hole in this logic is that it will skip any files
which were defuncted in pt after bl4.  You could check
for them as follows
	grep <directory> /usr/sde/osf1/build/ptos/logs/DEFUNCT

If you find any files you can do the bco for these as above.

Any files new to pt after bl4 will give errors and no file
will be bco'd.

-josh

----------
To: Joshua M. Friedman OSF/UNIX SDE <[email protected]>
Cc: [email protected]
Subject: Re: how to create a "backing tree"? 
Date: Mon, 12 Jun 95 14:33:13 -0400
From: [email protected]

>Do you need the *entire* src tree - kernel & commands?

I would prefer to have access to the entire tree.

A lot of times, I get asked "What baselevel did <something> go
into?"  Sometimes I need to ask the question to myself.  Usually,
this occurs AFTER the normal backing trees get blown away.

It would be great if I could say

	bco -u -rPTOS_BL4 <directory>

and then everything in the directory gets pulled out.

-mike