Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!apple!agate!ucbvax!ATHENA.MIT.EDU!wdc
From: wdc@ATHENA.MIT.EDU (Bill Cattey)
Newsgroups: comp.soft-sys.andrew
Subject: Re: collection of .dog files
Message-ID: <8bdQqIIGG02=FKVZYw@athena.mit.edu>
Date: 29 Jan 91 19:31:32 GMT
References: <UbdB48QB0KGWIJ4VlJ@holmes.parc.xerox.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 15

Excerpts from mail: 28-Jan-91 collection of .dog files Bill
Janssen@parc.xerox. (328)

> I'd like to suggest we create the directory ${ANDREWDIR}/dog/, and put
> all of them in there during the install phase.

I think it would be a good option to have.  However I would like to have
it be OPTIONAL.  Right now I am very comfortable having my developers
attach my build tree, and my users not use the .dog files.  I have a
hard enough time talking my systems people out of 30 MEG per platform to
export an Andrew NFS filesystem.  Adding in the dog files by default
would result in my having to remove them from the destination directory
by hand.

-wdc