Path: utzoo!utgpu!jarvis.csri.toronto.edu!neat.cs.toronto.edu!jonah
Newsgroups: ut.software.x-windows
From: jonah@cs.toronto.edu (Jeff Lee)
Subject: building R4
Message-ID: <90Jan4.164246est.3025@neat.cs.toronto.edu>
Date: 4 Jan 90 21:43:26 GMT
Lines: 33

I told Brian and Dave we would try to build the core in /h/xwindows/X.V11R4
and then move it to /csri3/X.V11R4 once it seems ok.  We will do the same
deal as last time, turning off tracking on X and letting church and clients
be the guinea pigs.  The "blessed" location for the lndir'd source tree is
/local/src/X.V11R4, so for the moment (on CSRI), this is a symlink to
/h/xwindows/X.V11R4.  Later, it will be a symlink to /csri3/X.V11R4.
Once things "work" on CSRI, we will turn on tracking and ANT will build
it for their machines.  Configuration files should be altered to believe
that TOPDIR is /local/src/X.V11R4.

The master source is in /ai/lambda/X.V11R3.  (Ken has exported /ai/lambda to
dbs, dgps, csris, eecgs, and whites.)  This MAY change, so it is strongly
suggested that you use an lndir through a symlink such that
/local/src/X.V11R4/SRC -> /ai/lambda/X.V11R4.  There is a recursive shell
script in xwindows@csri:bin/lnrel which can help with this.  [N.B.  Unlike
lndir it takes ONE argument which is the FROMDIR, the TODIR is assumed to be
".".

So for example:

	cd /local/src/X.V11R4
	ln -s /ai/lambda/X.V11R4 SRC
	lnrel SRC

or
	cd /local/src/X.V11R4
	ln -s /ai/lambda/X.V11R4 SRC
	(mkdir mit ; cd mit ; lnrel ../SRC/mit)

Also unlike lndir, lnrel makes REAL directories for RCS, so changes made in
lndired copies (e.g. for local configurations) will NOT be shared. (Finally!)

j.