AUR (en) - otf-fira-code-git

Search Criteria

Package Details: otf-fira-code-git 5.2.r54.g4e04092-1

Git Clone URL:	https://aur.archlinux.org/otf-fira-code-git.git (read-only, click to copy)
Package Base:	otf-fira-code-git
Description:	Monospaced font with programming ligatures
Upstream URL:	https://github.com/tonsky/FiraCode
Keywords:	code fira font otf
Licenses:	OFL
Conflicts:	otf-fira-code
Provides:	otf-fira-code
Submitter:	ulis
Maintainer:	alerque
Last Packager:	alerque
Votes:	13
Popularity:	0.000000
First Submitted:	2014-11-12 05:31 (UTC)
Last Updated:	2024-03-28 01:28 (UTC)

Git Clone URL:

https://aur.archlinux.org/otf-fira-code-git.git (read-only, click to copy)

Package Base:

otf-fira-code-git

Description:

Monospaced font with programming ligatures

Upstream URL:

https://github.com/tonsky/FiraCode

Keywords:

code fira font otf

Licenses:

OFL

Conflicts:

otf-fira-code

Provides:

otf-fira-code

Submitter:

ulis

Maintainer:

alerque

Last Packager:

alerque

Votes:

Popularity:

0.000000

First Submitted:

2014-11-12 05:31 (UTC)

Last Updated:

2024-03-28 01:28 (UTC)

Latest Comments

« First ‹ Previous 1 2

ulis commented on 2015-04-01 14:26 (UTC)

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.