On Wed, 2022-02-16 at 15:49 +0100, Martin Wilck wrote:
On Wed, 2022-02-16 at 15:16 +0100, Dominique Leuenberger / DimStar
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.
yast2-qt-branding-openSUSE requires two of them:
rpm -qR yast2-qt-branding-openSUSE adobe-sourcesanspro-fonts google-opensans-fonts
Which matches the requirements in /usr/share/YaST2/theme/current/wizard/installation.qss * { font-family:"Source Sans Pro",sans; font-size: 10.5pt } #DialogHeadingLeft { font-family: "Open Sans Condensed", Sans-serif; font-size: 18pt; color: #333; qproperty-alignment:AlignLeft; font-weight:bold; } (and some more definitions) - so, this package asking for those two fonts sounds correct and yast2-theme the third one:
rpm -qR yast2-theme google-poppins-fonts
At least with a very quick glance, I can't see why this one seems needed; Sounds like a bug report for the YaST Team to validate. Cheers, Dominique