<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Don't warn if cachedir isn't specified"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90148#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Don't warn if cachedir isn't specified"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90148">bug 90148</a>
from <span class="vcard"><a class="email" href="mailto:freedesktop@behdad.org" title="Behdad Esfahbod <freedesktop@behdad.org>"> <span class="fn">Behdad Esfahbod</span></a>
</span></b>
<pre>(In reply to Akira TAGOH from <a href="show_bug.cgi?id=90148#c3">comment #3</a>)
<span class="quote">> (In reply to Behdad Esfahbod from <a href="show_bug.cgi?id=90148#c2">comment #2</a>)
> > (In reply to Akira TAGOH from <a href="show_bug.cgi?id=90148#c1">comment #1</a>)
> > >
> > > I'm not sure what's the purpose of the warning/error for that though, if it
> > > is to detect the installation error,
> >
> > It might be ok for the system-wide config file. I suppose the aim is to
> > make sure systems set global cachedir, as to prevent every user to have
> > their own cache of all the system fonts. But we should definitely skip the
> > warning for custom config files.
>
> Right. but there are no way to know if it is custom or not. hence:</span >
It kinda is. If FONTCONFIG_FILE / FONTCONFIG_PATH are not set, and we were
initializing default config, we should warn.
<span class="quote">> > > is it a good idea to add an API like FcInitLoadConfigFromMemory()
> >
> > That API is certainly desirable.
>
> the above and the following suggestion. we can use it internally and move
> warnings out of it.
>
> > > FcInitWithMinimalConfig() or so may be more useful perhaps.
> > >
> > > Any thought?
> >
> > What would go into the minimal config?
> >
> > I discussed this in detail in my blog post. I don't think there's a clear
> > line between minimal config and full config.
>
> read it. well, I meant to make it convenient but may be better leave it to
> users then. so just reading the config from memory may be good.</span >
My current thinking is that for most use cases, reading full config (but not
fonts) might be what user wants. The major exception would be font viewers,
which probably can do without any config.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>