New issue
Advanced search Search tips

Issue 780603 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

remove legacy encoding mapping files in /usr/share/fonts/util/

Project Member Reported by js...@chromium.org, Nov 1 2017

Issue description

Chrome OS image has mapping files for legacy encodings in /usr/share/fonts/util.  I can't think of a reason to keep these mapping files. Perhaps, they're used for X11 BDF/PCF fonts, but CrOS does not have any.  


I don't know which package installs them, though. 

The total disk footprint is 200 kB. So, it's not huge. 
 

Comment 1 by js...@chromium.org, Nov 1 2017

Summary: remove legacy encoding mapping files in /usr/share/fonts/util/ (was: /usr/share/fonts/util/ : remove it )
$ qfile-betty -Rq /build/betty/usr/share/fonts/util/
media-fonts/font-util

$ qdepends-betty -a -Q media-fonts/font-util
 * DEPEND
x11-libs/libxkbcommon-0.4.3-r2
x11-libs/libX11-1.6.0-r1
 * RDEPEND
 * PDEPEND

so doesn't seem like it ends up in the rootfs of images, and i don't see the /usr/share/fonts/util/ dir on my local CrOS VM.  trimming it from those two packages would save us some resources (disk space/etc...) in the SDK itself, but wouldn't make a diff to runtime images.
Components: OS>Systems

Sign in to add a comment