Subject: Re: System-wide cache files for configure
To: Hubert Feyrer <firstname.lastname@example.org>
From: Julio M. Merino Vidal <email@example.com>
Date: 02/21/2004 22:36:55
On Saturday 21 February 2004 21:50, you wrote:
> On Sat, 21 Feb 2004, Julio M. Merino Vidal wrote:
> > Any comments about it will be welcome. Testing could be good too! ;-)
> Have you tested this?
> When I tried the idea of using a site-wide config.cache some time ago, it
> didn't work. IIRC the reason was that later runs detected that some
> pkg-related setthings had changed ``Woah, but that pkg wasn't installed
> before! Aborting...'' (Something like that; try & see)
Yeah, it may bring problems. This is why the configure script installed by
the package just checks for things that are unlikely to change over time
(like functions in libc, system headers, size of standard types, etc). Of
course the user might add a check to cache if gtk2 is present, for example,
but that will surely bring problems when updating and/or removing the package.
I don't think remember things like "maximum command length", "readdir_r is
not present", "err.h exists" can bring problems. And if it does, it's really
easy to rebuild the cache with up-to-date results.
Julio M. Merino Vidal <firstname.lastname@example.org>
The NetBSD Project - http://www.NetBSD.org/