Not sure if anyone is willing to do the work to fix the underlying problem here, but I have for some time been unable to use discord-bin because the fonts are all messed up. I stumbled across this: https://www.reddit.com/r/discordapp/comments/7w9c5f/fonts_are_really_screwed_up_on_linux/?ref=share&ref_source=link So on a hunch I tried (the equivalent of) the following: sudo ebuild "$(portageq get_repo_path / gentoo)"/media-libs/freetype/freetype-2.8.ebuild clean install && \ \ sudo cp "$(PORTAGE_TMPDIR)"/portage/media-libs/freetype-2.8/image/usr/lib64/libfreetype.so.6.14.0 $(portageq envvar EPREFIX)/opt/discord/share/discord/libfreetype.so.6 && \ \ sudo ebuild "$(portageq get_repo_path / gentoo)"/media-libs/freetype/freetype-2.8.ebuild and, whaddayaknow, the problem is solved. ime it would be unfortunate to give discord-bin a ( <=media-libs/freetype-2.8 ) DEPEND when this work-around solves it so much more elegantly... so I hope that is not the result of this repor Anyhow I wanted to at least share this workaround with anyone out there who may be similarly afflicted.
(In reply to Greg Turner from comment #0) > \ > sudo ebuild "$(portageq get_repo_path / > gentoo)"/media-libs/freetype/freetype-2.8.ebuild meant to say "clean" at the end :)
(In reply to Greg Turner from comment #0) > "$(PORTAGE_TMPDIR) should be $(portageq envvar PORTAGE_TMPDIR). Bleh.... I think my original post is too confusing/buggy. So, to clarify: the workaround was: STEP ONE run the =media-libs/freetype-2.8 ebuild up to the install phase, creating the file ${PORTAGE_TMPRDIR}/portage/media-libs/freetype-2.8/image/usr/lib64/libfreetype.so.6.14.0 STEP TWO copy/rename that file so it becomes: /opt/discord/share/discord/libfreetype.so.6
Please bug upstream about it.
