[Fontconfig] [PATCH] never try to validate cache files when using fc-cache -f

Patrick Lam plam at MIT.EDU
Thu Feb 2 09:47:42 PST 2006

Dirk Mueller wrote:
> Hi, 
> 2006-02-02  Dirk Mueller  <dmueller at suse.com>
> 	* fc-cache/fc-cache.c (scanDirs): Don't check for
> 	cache validity if force is in effect. 

This patch doesn't do what you're saying.  The effect of this patch is
to always blow away cache files when -f is given, and that's going to be
problematic on multi-arch installations.  The check a couple of lines above:

	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.

-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.


More information about the Fontconfig mailing list