
On Wed, 2022-02-16 at 08:58 -0500, Felix Miata wrote:
Johannes Meixner composed on 2022-02-16 13:51 (UTC+0100):
only an addedum to emphasize a specific point:
Dominique Leuenberger / DimStar wrote:
* Pkg X needs A to run => Requires ... The 'Requires' case is pretty obvious
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)
Also, glibc-locale-base gets the job done, yet several packages require glibc-locale.
That's just been cleaned up for example for RPM; Looking at the entire distro, I can see: zypper se -t package -x --requires glibc-locale 12 packages and 2 patterns requiring glibc-locale. Surely something that can be cleaned up. Feel free to lead the effort!
Cheers, Dominique