media-fonts/baekmuk-fonts-2.2-r1 inherits media-gfx/ebdftopcf which uses X Thus, the "-X" flag will have no effect, Xorg will get installed even with "-X". (not acceptable for CLI-only install on my server...)
We are working on fonts, see Bug 112675, comment #8
This is invalid. If you look at the revision before my fixes, baekmuk-fonts-2.2, and try to emerge it without having X installed, it generates bad font files - yes this is a bug, and needs to be fixed. The old ebuild runs this: bdftopcf $i | gzip -c -9 > ${i//bdf/pcf}.gz || die Which didn't catch that bdftopcf didn't exist, and just generated empty .gz files, causing you to never get the baekmuk fonts anyway. If you need the baekmuk fonts anyway and you're on ~arch, unmask the modular-X packages, as there the font-building tools are seperate.
app-text/ghostscript-afpl-8.53 USE="cjk cups -X -gtk -jpeg2k%" -> needs media-fonts/baekmuk-fonts-2.2-r1 [2.2] USE="unicode -X" -> needs X... That is completely screwed. I don't want X installed on my server ... maybe you could at least remove the "X"-flag which is useless, as X is used no matter if the flas is set or not.
Please see bug 119033. I've passed this discussion to the fonts and cjk herds, as they need to make a call on what to do about this due to the interactions with ghostscript-afpl. For the moment do try the modular-X route, as that will ensure that you don't have X on your machine, while still getting you the fonts properly.
