Package Details: ttf-google-fonts-git 20170626-2

Git Clone URL: https://aur.archlinux.org/ttf-google-fonts-git.git (read-only)
Package Base: ttf-google-fonts-git
Description: TrueType fonts from the Google Fonts project (git version)
Upstream URL: https://github.com/google/fonts
Keywords: fonts google ttf
Licenses: various
Conflicts: adobe-source-code-pro-fonts, adobe-source-sans-pro-fonts, googlefontdirectory, jsmath-fonts, lohit-fonts, oldstand-font, openarch_fonts, otf-bitter, otf-goudy, ttf-andika, ttf-anonymous-pro, ttf-cantarell, ttf-cardo, ttf-chromeos-fonts, ttf-comfortaa, ttf-croscore, ttf-droid, ttf-fira-mono, ttf-fira-sans, ttf-google-fonts-hg, ttf-google-webfonts, ttf-google-webfonts-git, ttf-google-webfonts-hg, ttf-inconsolata, ttf-kimberly_geswein_print, ttf-lato, ttf-lekton, ttf-lora-cyrillic, ttf-medievalsharp, ttf-merriweather, ttf-merriweather-sans, ttf-noto, ttf-nova, ttf-oldstandard, ttf-opensans, ttf-oswald, ttf-overpass, ttf-oxygen, ttf-oxygen-git, ttf-pt-mono, ttf-pt-sans, ttf-ptsans, ttf-quintessential, ttf-roboto, ttf-roboto-mono, ttf-signika, ttf-sil-fonts, ttf-sortsmillgoudy, ttf-source-code-pro, ttf-source-sans-pro, ttf-ubuntu-font-family, ttf-vollkorn
Provides: adobe-source-code-pro-fonts, adobe-source-sans-pro-fonts, googlefontdirectory, jsmath-fonts, lohit-fonts, oldstand-font, openarch_fonts, otf-bitter, otf-goudy, ttf-andika, ttf-anonymous-pro, ttf-cantarell, ttf-cardo, ttf-chromeos-fonts, ttf-comfortaa, ttf-croscore, ttf-droid, ttf-fira-mono, ttf-fira-sans, ttf-font, ttf-google-fonts-hg, ttf-google-webfonts, ttf-google-webfonts-git, ttf-google-webfonts-hg, ttf-inconsolata, ttf-kimberly_geswein_print, ttf-lato, ttf-lekton, ttf-lora-cyrillic, ttf-medievalsharp, ttf-merriweather, ttf-merriweather-sans, ttf-noto, ttf-nova, ttf-oldstandard, ttf-opensans, ttf-oswald, ttf-overpass, ttf-oxygen, ttf-oxygen-git, ttf-pt-mono, ttf-pt-sans, ttf-ptsans, ttf-quintessential, ttf-roboto, ttf-roboto-mono, ttf-signika, ttf-sil-fonts, ttf-sortsmillgoudy, ttf-source-code-pro, ttf-source-sans-pro, ttf-ubuntu-font-family, ttf-vollkorn
Submitter: sebstar
Maintainer: morealaz
Last Packager: morealaz
Votes: 508
Popularity: 5.553186
First Submitted: 2013-04-27 20:41
Last Updated: 2017-07-06 08:05

Required by (194)

Sources (1)

Pinned Comments

FadeMind commented on 2017-01-25 19:27

Please do not mark GIT based packages as OUT OF DATE. User should
rebuild GIT package manually instead of waiting for bump in AUR.

Exceptions: package build issues, major changes in conflicts/provides fields.

Thank you.

EDIT @ 16-02-2017

Package will be updated in 30 days period

Latest Comments

morealaz commented on 2017-07-06 08:08

@GeneArch as I see, this package only contains noto sans and serif but no other noto fonts. so I remove it as conflict and add it as dependency. I also remove noto fonts which shipped with this package like the Cantarell fonts.
thanks for noticing this

GeneArch commented on 2017-07-06 03:10

This creates a conflct with noto-fonts but does not provide all the fonts in the noto-fonts package - it only provides NotoSans and NotoSerif - all the other fonts are not provided - is there a way to provide all the missing fonts or make noto-fonts a dependency perhaps?

thanks

morealaz commented on 2017-06-18 07:59

@amosbird: done, thanks for noticing.

amosbird commented on 2017-06-05 08:22

Package ttf-lora-cyrillic conflicts with it. Please add them to conflicts and provides.

plp commented on 2017-02-16 08:58

Dear FadeMind,

I think you really *are* updating this file way too often, and some of us really *don't* have time to wait for it to be built every time we run yaourt.

Could you please reconsider?

jakebailey commented on 2017-02-14 20:12

I'm a bit confused. Why does the package version need to be manually updated when the package is a *-git package anyway? Shouldn't it be based on whatever changes are occurring in the Github repo? As was said before, the user is in charge of rebuilding the git package instead of waiting for a bump. I would only think that the PKGBUILD would be changed when a new conflict is discovered, or some other packaging change. (It's already a little weird that pkgver() builds off of a date instead of a commit description/hash, but I personally don't care as long as I can update when there's a change.)

If I'm wrong, then that's fine, I just want to understand the reasoning and maybe find a fix if it's not right.

bred commented on 2017-02-14 20:06

Please do not upgrade this package every 2 days.
One time every two weeks is more than enough!

Tnx.

FadeMind commented on 2017-02-14 06:40

@sez11a cause I have time for this ;)

sez11a commented on 2017-02-13 20:36

Hey @FadeMind, regarding your last comment, why does this package keep getting updated so frequently now?

FadeMind commented on 2017-01-25 19:27

Please do not mark GIT based packages as OUT OF DATE. User should
rebuild GIT package manually instead of waiting for bump in AUR.

Exceptions: package build issues, major changes in conflicts/provides fields.

Thank you.

EDIT @ 16-02-2017

Package will be updated in 30 days period

All comments