On Fri, 12 Aug 2005, Bryce Harrington wrote:
On Thu, Aug 11, 2005 at 10:01:14PM -0400, MenTaLguY wrote:
OK, 0.42.1 is pretty much ready to go, except there are two remaining issues I want to get nailed down first:
- Mac OS X folks: is it possible for us to add some workaround for
the user having to run "sudo /usr/X11R6/bin/fc-cache" manually on Tiger?
Sorry for my silence on this, I've been devoting all my time to the Summer of Code stuff. I had a look at this on Friday night and a little bit of today on the two Tiger machines I have access to. I can't reproduce the symptoms at all -- new local font config caches *always* get regenerated for me on these machines, even without the presence of /etc/fonts/fonts.conf. All I can think is that maybe there are different versions of Apple's X11 floating around with different behaviour.
So, I've done the following (commited to CVS). On Tiger, when Inkscape is launched, after checking X11 is available, a dialog is brought up informing users of the fontconfig problem. The dialog has a button labelled "run fc-cache". If chosen, an OS X authentication dialog in launched and fc-cache is run following the authentication. A file is stored in ~/.inkscape to mark that fc-cache has been run. Thus, once you you've gone though the process it won't try this again.
Cheers, Michael