2011/11/12 Friedrich Romstedt <friedrichromst...@gmail.com>: > $ stat -f "...." /Library/Fonts/NISC18030.ttf > Last accessed or modified: 1321107464 = 12 Nov 2011 > Last changed: 1264652963 = 28 Jan 2010 > Time of Birth: 1292365840 = 14 Dec 2010
The file might have been created earlier; the date 14 Dec 2010 is the day where I reinstalled my Mac after a HDD crash from backup. I have checked if I have backups older than that on one of the Time Machine disks but that is negative. But since Time Machine uses hardlinks to link the files between different backups the file backed up in the oldest backup from 27 Dec 2010 might have still the date of birth we're looking for. Assumed it didn't issue a completely new backup after restoring from the old one. I'm interested in this because I wonder how I ever got a working fontcache. It might be that I compiled matplotlib first differently, with python.org Python, hence gcc-4.0, and if we assume that it works under gcc-4.0, I would have ended up with a proper fontcache, and was free to compile with gcc-4.2 + 10.5 deployment target. Then the fontcache lived on all that years since Mid 2009 untouched. Until now, where it attempted to recreate it, with the gcc-4.2 + 10.5 targeted matplotlib, failing on that. I guess that the NISC18030.ttf in the backup has the date of birth of the first backup ever, meaning that it was probably present from the very beginning. This is suggested by the posts back to 2005, where the file existed on that ``bsd`` machine of William Stein, iirc. I strongly believe I just got a working intermediate matplotlib, which created the everlasting (or not) fontcache. Friedrich ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
