On 8/9/09 06:38, Michael Wybrow wrote:
Let me know of any new issues.
(nitpicking) since rev. 22205 of 'trunk/packaging/macosx/Resources/script' the launcher script now generally tests
| # Warn the user about time-consuming generation of fontconfig caches. | test -f "${HOME}/.inkscape/.fccache-new" || exit 12
but AFAIK
1) .fccache-new was used as flag for fc-cache (X11) on Tiger 2) ~/.inkscape was changed to ~/.config/inkscape in 0.46+devel
The test fails if I rename an existing ~/.inkscape (to appear like a user who never has run Inkscape 0.46 on Leopard), even if I just used Inkscape 0.47pre2 before and have valid font cache files in ~/.fontconfig:
Inkscape 0.47pre2 displays the error message about "The first time this version of Inkscape is run it may take several minutes... ", creates ~/.inkscape and an empty ~/.inkscape/.fccache-new (as coded in ScriptExec/main.c) and then continues to use ~/.config/inkscape and ~/.fontconfig for preferences and font cache.
IMHO Inkscape 0.47 should not create ~/.inkscape if 0.46 was never run by the user. Instead, it would be better to a) move the fccache-new flag file to ~/.config/inkscape or b) continue to test for the existence of ~/.fontconfig (on Leopard) and create the directory if it is missing.
related bug #226355 https://bugs.launchpad.net/inkscape/+bug/226355 “inkscape 46-2 won't load in OSX Leopard 10.5.2, Xquartz 2.2.1”
~suv