[Fontconfig] [PATCH] never try to validate cache files when using
dmueller at suse.de
Thu Feb 2 11:48:17 PST 2006
On Thursday 02 February 2006 18:47, Patrick Lam wrote:
> if (!force && FcDirCacheValid (dir) && FcDirCacheHasCurrentArch (dir))
> checks for cache validity and ought to ensure that -f will try to save
> the cache files. Of course it might fail for some other reason.
Hmm, indeed. but I want one switch to make sure no corrupt cache files stay
around, as we have way too many problems with them.
The man page says:
Force re-generation of apparently up-to-date cache files, overriding the
> -f works for me. Does it not work for you? What should the semantics
> of -f be? Perhaps there should be -f and --really-force, which would
> always remove cache files; that's certainly not what we want to give
> when we make install.
what does make install have to do with it (curious)? Indeed, the normal
behaviour whould be to just run "fc-cache" I think.
More information about the Fontconfig