🚀 go-pugleaf

Are there any application notes covering the suggested convention for
supporting heterogeneous sun3/sun386 target/development environments?
What is the suggested arrangement of source, object, SCCS, and binary
execut- able directories?  Should the path environment variable set
conditionally based on 'arch'?  When doing a "make", using source NFS
mounted and shared between both architectures, where should the output
objects be placed?  (I imagine that NSE addresses these issues, but there
must be some recommended way of dealing with them that doesn't require
NSE).

Are the config files .defaults, .mailrc, .sunview, etc. compatible across
sun3/sun386 architectures?  If not, what is the prescribed way of
switching between sets depending on the host 'arch', assuming that a user
has one home directory located on the network?

Posting of any related experiences would be helpful.  Any email received
on the subject will be summarized.

	Thanks (wishful thinking)

	Paul Matz
	PPG Biomedical Systems
	Pleasantville, NY.
	914-741-4685
	ppgbms!paul or
	ppgbms!paul@philabs.Philips.COM