file triggers for updating fontconfig cache in rawhide

[nicolas.mailhot at laposte.net]

----- Mail original -----
De: "Matthew Miller" 

> 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)

However, that's just a suspicion for now. I haven't really investigated so far, and the system noto killed my side is not so powerful (chromebook)

At minima all packages with fonts should be mass rebuilt now, otherwise fontconfig cache refresh will be called both with the new method via triggers in the fontconfig package, and by the scriplets in current font packages. But I doubt this doubling alone is sufficient to cause the effect we've both seen

To be fair the change was done due to missed cache updates, I'd have chosen heavy-handedness myself in that case.