Package Details: otf-fira-code-git 1.201.r0.g92df0e8-1

Git Clone URL: https://aur-dev.archlinux.org/otf-fira-code-git.git (read-only)
Package Base: otf-fira-code-git
Description: Fira Code: monospaced font with programming ligatures.
Upstream URL: https://github.com/tonsky/FiraCode.git
Keywords: code fira font otf
Licenses: custom:OFL
Submitter: ulis
Maintainer: jzhu98
Last Packager: jzhu98
Votes: 4
Popularity: 0.040423
First Submitted: 2014-11-12 05:31
Last Updated: 2016-08-31 06:55

Latest Comments

jzhu98 commented on 2016-08-08 12:51

Fixed. Thanks, @jonathan!

jonathon commented on 2016-07-18 10:23

Upstream repo structure looks to have changed so the *.otf files have moved. One possible solution would be:

install -Dm644 "$name" "$pkgdir/usr/share/fonts/OTF/$name"
->
install -Dm644 "distr/otf/$name" "$pkgdir/usr/share/fonts/OTF/$name"

Works-for-me PKGBUILD here: http://pastie.org/10910575

jzhu98 commented on 2015-12-25 19:25

Updated to the latest version 1.101, now with all five weights:
Regular, Light, Medium, Bold, and Retina.

ulis commented on 2015-04-01 14:26

May be. Actually, I've copypasted PKGBUILD from another font git package. Guidelines you referred are subject of discussion (https://wiki.archlinux.org/index.php/Talk:VCS_package_guidelines) and I'm not convinced that commit tags fit the best for package versioning.

But I have neither strong opinion about this topic nor passion to apply another versioning scheme. Btw, I can disown package if you have enough fuel to polish it and keep it up-to-date.

Voice commented on 2015-04-01 09:51

Great. Also, I think -git PKGBUILD versioning is supposed to be different?
https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git

ulis commented on 2015-04-01 06:29

fixed, thanks for the report

Voice commented on 2015-04-01 05:21

ERROR: Integrity checks (md5) differ in size from the source array.
updpkgsums --help
Thank you