Conference smurf::buildhelp

2469.0. "update on Digital UNIX submit pools build support changes" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed Aug 07 1996 15:47

Date Of Receipt: 	 7-AUG-1996 10:58:13.97
From: 	FLUME::jmf "Joshua M. Friedman Digital UNIX  07-Aug-1996 1057"
To: 	odehelp@DEC:.zko.flume, buildhelp@DEC:.zko.flume,
	useg_reng@mudrat.zk3.dec.com
CC: 	
Subj: 	update on Digital UNIX submit pools' build support changes

The attached plan, announced last week, is now going into effect.  If
anyone all of a sudden complains about not being able to build, and
they're backed by a submit tree, they should be directed to resb to be
backed by the appropriate nightly or baselevel or ssb tree.

Note that we've recently added .ssb links and odemount entries for all
the released pools, so, for example, you can access the ptos.bl12
milestone using "odemount ptos.ssb" and "mksb -back ptos.ssb <sb>".

-Josh

------- Forwarded Message

To: osf_developers@falpha.zk3.dec.com
Cc: odehelp, rmg, tresvik
Subject: Digital UNIX submit pools' build support changes 
Date: Fri, 02 Aug 96 13:15:40 -0400
From: "Joshua M. Friedman, Digital UNIX, 381-1548" <jmf>
X-Mts: smtp
Status: RO

UNIX developers who sometimes do builds while backed to submit pools
should be aware of the following changes which will be going into
effect early next week.

In many of the submit pools, eg steelos, ptos, v40supportos, we have
provided convenient support for users to do partial builds by providing
a symbolic link from 'obj' and 'export' to those same directories in
either a nightly tree or an ssb baselevel tree.

Next week we will be removing these links in an attempt to reduce extra
NFS traffic on the submit server, and to encourage more appropriate use
of the build model.

In most cases when building backed by the submit tree, you really
should be building backed by the actual nightly or baselevel tree, not
the submit tree, for several reasons: 

  o The submit tree export and obj links do not represent all the
    latest headers and libraries, based on submits since the last
    build; this can result in misleading test build results.

  o The submit server in zk3, secret, is quite busy with all the normal
    ODE pool traffic, and doesn't need to be burdened with extra
    unneccesary build traffic; this is not in its "job description".

  o In addition, the submit tree is not guaranteed to have a stable
    complete source code base at any given time.  I.e. a developer may
    be in the middle of submitting functionality, and builds may appear
    to be "broken" if attempted.

If you need some of the latest sources from the submit tree in your
sandbox build, you can copy them, "bco -u $NEW" them, or use the ODE
"uptodate" command, while backed to a nightly or baselevel tree.  It
will still be possible to build backed to the submit tree, but you're
on your own to set up your sandbox for that case; we really discourage
this activity.

Thank you very much.		-digital unix release engineering



------- End of Forwarded Message