On Wed, 2022-02-16 at 15:16 +0100, Dominique Leuenberger / DimStar
This is not the way it is for fonts. Packagers shouldn't be /requiring/ particular font families when any ordinary TTF or OTF font will serve the purpose of putting legible fonts where needed, but that's the way it is (or was until recently with one or more), with:
adobe-sourcesanspro-fonts cantarell-fonts google-opensans-fonts google-poppins-fonts hack-fonts noto-sans-fonts raleway-fonts
I suppose there may be more fonts "required" by DEs I've never installed.
I understand part of the frustration - but in case of e.g. GNOME, the theme clearly specifies a font as part of the css properties and the branding defines a default font. That one being required sounds plausible (especially considering how often the recommendation of -- no- recommends is being copied around)
Perhaps, but is the following also necessary? # zypper remove google-opensans-fonts The following 6 packages are going to be REMOVED: daps google-opensans-fonts suse-xsl-stylesheets yast2-qt-branding- openSUSE yast2-theme yast2-x11 # zypper remove adobe-sourcesanspro-fonts The following 4 packages are going to be REMOVED: adobe-sourcesanspro-fonts yast2-qt-branding-openSUSE yast2-theme yast2-x11 # zypper remove google-poppins-fonts The following 3 packages are going to be REMOVED: google-poppins-fonts yast2-theme yast2-x11 YaST seems to pull in 3 different font families. Martin