Humm, and seems like a slash is missing somewhere:
[behdad@home cache]$ pwd
/home/behdad/.local/var/cache
[behdad@home cache]$ ll
total 48
drwxrwxr-x 2 behdad behdad 4096 Dec 10 02:16 fontconfig
-rw-rw-r-- 1 behdad behdad 16384 Dec 10 02:16 fontconfig29cc395f695634896af6925bc549e484.cache-2
-rw-rw-r-- 1 behdad behdad 28672 Dec 10 02:16 fontconfig2a4a6418bbcce3c3e071c870ed3b6b61.cache-2
BTW, how are different users handled exactly? Isn't it possible
to harm other users?
behdad
On Sat, 10 Dec 2005, it was written:
> Hi,
>
> I'm testing the cache dir. First, the following error message is
> not quite accurate anymore:
>
> [behdad@home fc-cache]$ fc-cache
> Can't save cache in "/home/behdad/.fonts"
> Can't save cache in "/home/behdad/.fonts/farsifonts-0.4"
>
> A simple fix is to change "in" to "for", or better, print out the
> cache directory (once?).
>
> As for creating the cache dir, the simplest way is:
>
> Index: fc-cache/Makefile.am
> ===================================================================
> RCS file: /cvs/fontconfig/fontconfig/fc-cache/Makefile.am,v
> retrieving revision 1.10.4.1
> diff -u -p -r1.10.4.1 Makefile.am
> --- fc-cache/Makefile.am 9 Dec 2005 16:36:45 -0000 1.10.4.1
> +++ fc-cache/Makefile.am 10 Dec 2005 07:17:34 -0000
> @@ -29,6 +29,11 @@ SGML = ${FC_CACHE_SRC}/fc-cache.sgml
>
> AM_CPPFLAGS = -DPKGCACHEDIR='"${pkgcachedir}"'
>
> +pkgcache_DATA=stamp
> +
> +stamp:
> + touch $@
> +
> INCLUDES=-I${top_srcdir} $(FREETYPE_CFLAGS)
>
> bin_PROGRAMS=fc-cache
>
>
> which abuses the install features of automake to create the
> directory.
>
>
> --behdad
> http://behdad.org/
>
> "Commandment Three says Do Not Kill, Amendment Two says Blood Will Spill"
> -- Dan Bern, "New American Language"
> _______________________________________________
> Fontconfig mailing list
> Fontconfig@xxxxxxxxxxxxxxxxxxxxx
> http://lists.freedesktop.org/mailman/listinfo/fontconfig
>
>
--behdad
http://behdad.org/
"Commandment Three says Do Not Kill, Amendment Two says Blood Will Spill"
-- Dan Bern, "New American Language"
