algaos/algaos-ebuild-tree/eclass/font.eclass, branch next

font.eclass: Document _update_fontcache as internal function

2026-02-20T17:23:59Z

Signed-off-by: Ulrich Müller

eclass: standardize prologue/epilogue

2023-03-17T22:04:31Z

Closes: https://github.com/gentoo/gentoo/pull/30061 Signed-off-by: David Seifert

font.eclass: introduce FONT_OPENTYPE_COMPAT for converting old bitmap fonts

2022-11-20T01:02:38Z

>=x11-libs/pango-1.44 dropped support for old bitmap fonts. We can convert (or really, wrap/embed) fonts from the legacy .bdf and .pcf formats into the OTB wrapper format using x11-apps/fonttosfnt. This commit adds FONT_OPENTYPE_COMPAT to font.eclass which packages installing bitmap fonts can set to opt-in to conversion/wrapping. Note that the font conversion isn't perfect -- it's good enough in many cases, but in some cases they may require tweaking via fontconfig to get pixel size right, antialiasing settings, ... Adds IUSE=+opentype-compat to any ebuilds which set FONT_OPENTYPE_COMPAT; enabled by default given discoverability of this issue may be difficult and presumably any font package enabling FONT_OPENTYPE_COMPAT will be useless without it anyway. See also https://fedoraproject.org/wiki/BitmapFontConversion. Bug: https://bugs.gentoo.org/698922 Thanks-to: Kerin Millar Signed-off-by: Sam James

font.eclass: Remove racy pkg_postinst code

2022-11-08T23:48:51Z

Noticed on ChromeOS when installing a large number of font packages in parallel: /usr/share/fonts/noto/NotoSerifThai-Regular.ttf#new' from 0004 (------r--) to 2440 (r--r-S---) * ERROR: media-fonts/ipaex-004.01-r1::chromiumos failed (postinst phase): * failed to fix font files perms The "#new" filename is the hint. Portage uses "#new" suffixes when copying files to the system, and then renames them to their final filenames. This code was executing while another font was in the process of being copied to the system. Font packages should just ensure that they install files with correct permissions to begin with, and all except media-fonts/x11fonts-jmk already use 0644 permissions. media-fonts/x11fonts-jmk used 0444 (which was probably fine) until the previous commit which changes its installed files to 0644. Bug: https://bugs.gentoo.org/187774 Signed-off-by: Matt Turner

font.eclass: check for dir existence in _update_fontcache

2022-10-19T03:08:48Z

It's still subject to a narrow race but nowhere near as bad as removed-last-font-now- its-gone. Closes: https://bugs.gentoo.org/754702 Signed-off-by: Sam James

font.eclass: Support EAPI 8

2022-04-03T18:50:13Z

Closes: https://bugs.gentoo.org/806496 Signed-off-by: Matt Turner

*.eclass: @ECLASS-VARIABLE renamed to @ECLASS_VARIABLE

2022-03-24T03:58:34Z

Bug: https://bugs.gentoo.org/835396 Signed-off-by: Ulrich Müller

font.eclass: Cleanup double slashes, FONTDIR always starts w/ '/'

2021-03-26T21:32:07Z

Signed-off-by: Andreas Sturmlechner

font.eclass: use BDEPEND with EAPI 7

2021-03-26T21:32:03Z

The mkfontscale program and encodings paths are used in the native root during src_install, so they need to be in BDEPEND. Also stop documenting DOCS as an eclass variable since it is a part of EAPI 6 and only used in eutils.eclass for EAPI 5 support. Closes: https://bugs.gentoo.org/776412 Signed-off-by: David Michael Signed-off-by: Andreas Sturmlechner

font.eclass: Drop EAPI-6 support

2021-03-26T21:30:57Z

Drop FONT_S space-delimited-list fallback support. Signed-off-by: Andreas Sturmlechner