Re: Is fc-cache broken on -current?

[walt <wa1ter@xxxxxxxxxxxxx>]

Jeremy C. Reed wrote:
> On Thu, 28 Sep 2006, Bill Hacker wrote:
> 
>> walt wrote:

>>> The problem was that those config files should have been
>>> replaced during the update!

>> Ordinarily NOT by the 'update'. But by the 'updater',
>> .. with care to preserve whatever customization...


> In the case of fontconfig, the fonts.conf file should not be manually 
> edited by the admin as the customizations should be in local.conf.

Right.  'fonts.conf' has a big banner at the top, cautioning the
admin *not* to edit the file.  The concept of a 'config' file which
must not be edited is a bit bizarre, IMO.  That sort of 'config' is
done at compile-time (usually).

This means that the fontconfig package *should* replace at least
those 'do-not-edit' config files without asking.