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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Dirk Mueller wrote:
> 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. 

It would be great to have a --really-force flag, then.  The man page
doesn't think about the issues involved in multiarch cache files.

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

make install runs fc-cache -f -v, as I'd imagine postinst scripts would
as well.

Fontconfig mailing list

[Index of Archives]     [Fedora Fonts]     [Fedora Users]     [Fedora Cloud]     [Kernel]     [Fedora Packaging]     [Fedora Desktop]     [PAM]     [Gimp Graphics Editor]     [Yosemite News]

  Powered by Linux