Re: file triggers for updating fontconfig cache in rawhide

> On Thu, Sep 10, 2015 at 07:35:03PM +0200, nicolas.mailhot(a)laposte.net wrote: >> > I just discovered that trying to install the Noto font family in >> > Software will reliably kill a (relatively powerful) system. This will >> > fix that, right? >> I fear that's the cause, not the solution. The previous solution was >> very careful to only call fontconfig once per changed font directory. >> Unless the triggers are filtered they will launch once per font >> *file*. So a killer for packages with many font files (like noto) > The initial message here (see subject line, actually) says that the > change was made in Rawhide. My system was F23, so it's gotta be the old > thing not the new one, right? All of font packages needs to be rebuilt to complete the transition for this and doing it now may be a bit late? otherwise I'm willing to work on that though.