google-noto-fonts

Edit Package google-noto-fonts
No description set
Refresh
Refresh
Source Files
Filename Size Changed
LICENSE 0000004377 4.27 KB
_constraints 0000000109 109 Bytes
generate-fonts-and-specfile.sh 0000004827 4.71 KB
google-noto-fonts.changes 0000008759 8.55 KB
google-noto-fonts.spec 0000160410 157 KB
google-noto-fonts.spec.in 0000002573 2.51 KB
ttf.tar.gz 0247038182 236 MB
Revision 24 (latest revision is 30)
Dominique Leuenberger's avatar Dominique Leuenberger (dimstar_suse) accepted request 982913 from Gordon Leung's avatar Gordon Leung (Pi-Cla) (revision 24)
feat: create new metapackage noto-fonts with all Noto Fonts except CJK and Emoji
update: 20220524 -> 20220607
- Noto Sans and Noto Sans Myanmar have been updated
fix(spec): add LICENSE to every package, remove redundant doc package
- It is likely a legal requirement that the license must be included with the package (rather than only recommends)
- Using the %license macro and including the license in every subpackage is the norm
fix(sh): prevent redundant .svn files from being compressed into archive
chore(spec): use install instead of mkdir and cp
chore(sh): fix typo
Comments 4

Yunhe Guo's avatar

Should this package be named as "noto-fonts"? Because all its sub-packages are prefiexed with noto- rather than google-noto-


Jan Engelhardt's avatar

Most font packages are prefixed with the name of the vendor/group/foundry. https://en.opensuse.org/openSUSE:Packaging_Fonts#Naming_and_Central_Font_Repository


Yunhe Guo's avatar

If it should be prefixed with google-noto-, then all sub-packages should have the same prefix. It is a problem of inconsistent naming.


openSUSE Build Service is sponsored by