Is fc-cache broken on -current?

Jeremy C. Reed reed at reedmedia.net
Wed Sep 27 10:16:22 PDT 2006


On Thu, 28 Sep 2006, Bill Hacker wrote:

> walt wrote:
> 
> > Joerg Sonnenberger wrote:
> > 
> > > On Sun, Sep 24, 2006 at 03:05:44PM -0700, walt wrote:
> > > 
> > > > Can anyone confirm this error with the latest fontconfig
> > > > from pkgsrc?
> > > > 
> > > > # fc-cache -v /usr/pkg/xorg/lib/X11/fonts/TTF
> > > > /usr/pkg/xorg/lib/X11/fonts/TTF: caching, 22 fonts, 0 dirs
> > > > /usr/pkg/xorg/lib/X11/fonts/TTF: failed to write cache
> > > > fc-cache: failed
> > > 
> > > Works fine here. Can you delete all old font caches just to make sure
> > > that it doesn't try to reuse those?
> > 
> > 
> > Bah.  The problem was the old fontconfig config-files in
> > /usr/pkg/etc.  I noticed that the update announced that
> > there were existing config files so they were not touched.
> > 
> > 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 is still appropriate, if any.
> 
> That's why the general rule is to produce a message and NOT over-write.
> 
> Easy to get the new set that had been skipped spit-out again.
> 
> Much harder to recover lost ones automatically, and silently, over-written.


On deinstallation of a package, the package's registered configurations 
are compared with the versions in the share/examples directory.

If different, then it is removed.

On a package installation, if the configuration does not exist, it will be 
copied into place from the (newly installed) share/examples version.

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.





More information about the Users mailing list