Re: [PATCH] fontcache: allow to pass different fontconfig cache dir

[Martin Jansa <martin.jansa@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

On Mon, Mar 30, 2015 at 11:47:39AM +0100, Burton, Ross wrote:
> On 29 March 2015 at 02:27, Martin Jansa <martin.jansa@gmail.com> wrote:
> 
> > +FONTCONFIG_CACHE_DIR ?= "${localstatedir}/cache/fontconfig"
> >
> 
> So how is fontconfig told to read fonts from this location?

I think it's the same
--with-cache-dir
parameter which says where to generate the cache and then read it in
runtime.

I didn't change it in fontconfig recipe, because the default is already
matching with FONTCONFIG_CACHE_DIR, do you want me to pass
--with-cache-dir parameter? I agree that it could be less surprising for
people who want to change it, but on the other hand if upstream moves
default cache location in some newer fontconfig version, then the person
updating the recipe should check FONTCONFIG_CACHE_DIR value as well.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]