On Sun, 2007-09-30 at 09:06 +0100, William Pursell wrote:
> Eric Blake wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > According to William Pursell on 9/29/2007 11:14 AM:
> >> I'm talking about those files named $cache_file in
> >> my $CONFIG_SITE. Since they hold lines of th
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to William Pursell on 9/29/2007 11:14 AM:
I'm talking about those files named $cache_file in
my $CONFIG_SITE. Since they hold lines of the form:
ac_cv_func_foo=${ac_cv_func_foo=yes}
the cache is invalid if I remove the p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to William Pursell on 9/29/2007 11:14 AM:
> I'm talking about those files named $cache_file in
> my $CONFIG_SITE. Since they hold lines of the form:
> ac_cv_func_foo=${ac_cv_func_foo=yes}
> the cache is invalid if I remove the package
> cont
Bob Proulx wrote:
William Pursell wrote:
I often find myself removing a package and then deleting
all of my cache files, but I have a tendency to forget
to delete the cache files until a configure invocation
noticeably misbehaves.
Autoconf cache files? As in the 'autom4te.cache' directories c
William Pursell wrote:
> I often find myself removing a package and then deleting
> all of my cache files, but I have a tendency to forget
> to delete the cache files until a configure invocation
> noticeably misbehaves.
Autoconf cache files? As in the 'autom4te.cache' directories created
in the
Originally, I was planning to post this question to one of the
Debian lists, but the second part of the question is more
appropriate here, so I thought I would just start here.
I often find myself removing a package and then deleting
all of my cache files, but I have a tendency to forget
to dele
