Hi there. Currently, the "google-noto-fonts-all" meta-package installs many font duplicates. Fedora seems to prefer VF variants ( https://fedoraproject.org/wiki/Changes/VariableNotoFonts , https://fedoraproject.org/wiki/Changes/Noto_CJK_Variable_Fonts ), but the meta-package installs both Static and VF variants of the same fonts. Example from command "dnf repoquery --requires google-noto-fonts-all": ------------------------------------------------------ google-noto-serif-hebrew-fonts = 20250901-1.fc43 google-noto-serif-hebrew-fonts = 20251101-2.fc43 google-noto-serif-hebrew-vf-fonts = 20250901-1.fc43 google-noto-serif-hebrew-vf-fonts = 20251101-2.fc43 ------------------------------------------------------ I would like to request the creation of a meta-package that prioritizes VF variants and don't install their equivalent duplicates in Static variant. For example, the meta-package would install Hebrew VF fonts, but not Hebrew Static fonts. This eliminates the duplicates, while still keeping the Static fonts in a meta-package for the fonts that don't have VF variants. Additional note: the current "google-noto-fonts-all" should probably install the other "-all" meta-packages as well, since it includes all of their deps as well. Thanks. Reproducible: Always
Have you ever tried google-noto-fonts-all-vf?
Hi Akira, From my testing it seems "google-noto-fonts-all-vf" only installs all Noto fonts with VF variants, no static fonts included. I think you did not understand what I mean. My request is a new meta-package that avoids the duplicates (fonts with both VF and static variants), while prioritizing VF variants, and still ultimately installing the static fonts that also don't have a VF variant equivalent, ending up with all fonts available installed.
Trying to consider how we can implement this. However we can't guarantee the upgrading path because upstream sometimes drops a font and added back due to the some reasons. We already have a sort of the lines of Obsoletes: and Provides: for some packages and removed them later. This would means you may eventually have both VF and static font packages getting installed by a new meta-package and it is quite hard to settle the upgrading path issue.