From xemacs-m  Sun May 18 17:31:28 1997
Received: from ALPHA8.CC.MONASH.EDU.AU (alpha8.cc.monash.edu.au [130.194.1.8])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id RAA11782
	for <xemacs-beta@xemacs.org>; Sun, 18 May 1997 17:31:27 -0500 (CDT)
Received: from goaway.cc.monash.edu.au ("port 3779"@goaway.cc.monash.edu.au)
 by vaxh.cc.monash.edu.au (PMDF V5.1-7 #20655)
 with ESMTP id <01IJ1PUIRFVS8ZEB59@vaxh.cc.monash.edu.au> for
 xemacs-beta@xemacs.org; Mon, 19 May 1997 08:31:20 +1000
Received: (ajc@localhost) by goaway.cc.monash.edu.au (8.8.5/8.6.4)
 id IAA09852; Mon, 19 May 1997 08:31:20 +1000 (EST)
Date: Mon, 19 May 1997 08:31:20 +1000
From: Andrew J Cosgriff <Andrew.Cosgriff@cc.monash.edu.au>
Subject: Re: config.cache missing?
In-reply-to: Hrvoje Niksic's message of 18 May 1997 15:29:25 +0200
To: xemacs-beta@xemacs.org
Message-id: <ruiaflss98n.fsf@goaway.cc.monash.edu.au>
MIME-version: 1.0 (generated by tm-edit 7.106)
X-Mailer: Gnus v5.4.52/XEmacs 20.2
Content-type: text/plain; charset=US-ASCII
X-Attribution: ajc
X-URI: <URL:http://www-personal.monash.edu.au/~ajc>
X-PGP-Key-ID: C7BD53F5
X-Face: 
 PBPJ+.AE`FBN4$}H<dIo+^`A-G%mJTXXP$^4bBox##5=oF{G\[:0|sNlr%~H1,>rwwEh<qq.dHRpu8ftJ\'14l]<x(nRD>J)x?-5$MQ%Z)svNR@Q\WG6[GDr,}a@8ULwGWBsk,Pqxm!Z<lnD(Skwwe$j+<0g6N6z}>-
X-Tom-Swifty: "I've just been drafted,"  Tom said impressively.
Lines: 35
References: <kigiv0hw00j.fsf@jagor.srce.hr>
 <199705181302.GAA09835@xemacs.eng.sun.com> <kigzpttue0e.fsf@jagor.srce.hr>
 <199705181321.GAA09841@xemacs.eng.sun.com> <kigwwowvrgq.fsf@jagor.srce.hr>

"Hrv" == Hrvoje Niksic <hniksic@srce.hr> writes:

mb> Caching results is always slower and more reliable than not.

Hrv> I don't understand this sentence.  Have you meant ``less
Hrv> reliable''?

mb> I think GNU software configuration has become effectively a lot
mb> less reliable for many people because of the introduction of
mb> caching.

Hrv> I don't see on what grounds you base this claim.  I've never had
Hrv> problems with configure caches, especially as `make distclean'
Hrv> typically removes config.cache.  Site-wide caches are installed
Hrv> by people who know what they are doing anyway.

mb> I've run configure hundreds of times over the last weeks, and I
mb> personally do not want caching.

Hrv> Then you are either running it on very fast machines or are
Hrv> exceptionally patient.  For me checking might be important
Hrv> because of speed.  I was going to try to install a site-wide
Hrv> cache, too.  It would feel stupid that after all the fuss the
Hrv> program I use most doesn't facilitate it.

I used to have a machine-wide cache for my builds last year, but ran
into all sorts of weird problems with a couple of programs (zsh comes
to mind) that turned out to be due to bogus things in the cache, and
so I stopped doing it...

Andrew
-- 
 - Andrew J. Cosgriff -                  ajc@bing.wattle.id.au    (PGP/MIME ok)
 +61 3 9905 1165 (bh) 9905 4746 (fax)    http://www-personal.monash.edu.au/~ajc
                             Is this TERMINAL fun?

