Mike FABIAN wrote: >>The system I'm on here is amd64 with an ia32 chroot. /home is shared >>between the amd64 install and the chroot. >> >>1. remove a fonts.cache-2 file (dir cache) from both the install and >>the chroot >>2. fc-list in the install >>3. fc-list in the chroot >>4. fc-cat ~/.fonts.cache-2 in the install >> >>You'll see that the install's .fonts.cache-2 gets trampled by the >>chroot's .fonts.cache-2. > > > I cannot reproduce this. It works fine for me. I am running 32bit and > 64bit applications using fontconfig alternatetly and they don't > trample each others data in ~/.fonts.cache-2. In that case, it could just be the computer I was using or some aspect of its configuration. I'll try to look into it a bit more. >>Note also that the line you patched was a fix to 'severe perf >>regression when global fonts.cache-2 files are missing', which you and >>I tested back in October 2005. I'm going to test that behaviour as >>well (put junk in .fonts.cache-2, see what happens). > > If ~/.fonts.cache-2 is "missing", it doesn't have to be deleted. > > Deleting it when the current architecture cannot be found > cannot be correct in my opinion. Yes, that's clearly wrong. The problem was a related case, when it couldn't make sense of the cache file and just did weird things. pat _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
