FS#40134 - [terminus-font] fc-cache -f
Attached to Project:
Community Packages
Opened by cupcake (muffins) - Tuesday, 29 April 2014, 00:59 GMT
Last edited by Alexander F. Rødseth (xyproto) - Sunday, 04 May 2014, 11:57 GMT
Opened by cupcake (muffins) - Tuesday, 29 April 2014, 00:59 GMT
Last edited by Alexander F. Rødseth (xyproto) - Sunday, 04 May 2014, 11:57 GMT
|
Details
Description:
the terminus-font package forces a full cache update. terminus only installs fonts to one directory, so if you're set on keeping -f, then please only force that directory and not the whole cache. Otherwise, in place of the current fc-cache line, please: fc-cache -s /usr/share/fonts/misc I keep an icons bdf font that I use alongside terminus and haven't noticed any ill effects using the above in its install file. As an example: # pacman -Rs icons-git # pacman -Rs terminus-font (everything now nuked) # pacman -S terminus-font --noscriptlet # pacman -S icons-git (everything back to normal) Not sure if I should take this to the ML, because quite a few font packages use -f. I hope I'm right about it being unneccessary. |
This task depends upon
With just over 1500 fonts (including styles), running `fc-cache -rf` takes upwards of 1 minute to complete.
As `-f` only really makes sense when the cache has become corrupt (which should mandate user intervention) it would be kinder to just run `fc-cache` on its own or alternatively `fc-cache -s` which avoids tampering with XDG_DATA_HOME/fons and HOME/.fonts
Running `fc-cache` itself is also only necessary because you're updating a cache owned by root, its not necessary to even use `fc-cache` as a user.
Here's a simple comparison after adding one font:
fc-cache 0.01s user 0.02s system 91% cpu 0.040 total
fc-cache -rf 32.28s user 1.40s system 44% cpu 1:15.63 total