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)

Required by (2)

Sources (1)

Latest Comments

1 2 Next › Last »

damax commented on 2023-03-23 00:00 (UTC) (edited on 2023-03-23 00:18 (UTC) by damax)

Now that otf is not provided upstream anymore, how can we get the variant ligatures?

Found out that it's already usable in newer versions with stylistic sets. Should this package be removed?

Petkr commented on 2022-08-06 16:09 (UTC)

./script/build needs to be changed to ./script/build.sh. Also, gftools seems to have removed the fix-dsig option which causes a build failure, so still can't build.

alerque commented on 2020-07-29 21:09 (UTC) (edited on 2020-07-29 21:17 (UTC) by alerque)

@allspark That should be singular script not scripts, thanks for the report. But even when I upload that fix in a minute you'll still have a problem because upstream master is broken as of now. See this upstream issue report for why (and a hacky fix if you want to do that).

allspark commented on 2020-07-28 16:36 (UTC) (edited on 2020-07-28 16:36 (UTC) by allspark) 

==> Extracting sources...
  -> Creating working copy of FiraCode git repo...
Cloning into 'FiraCode'...
done.
==> Starting pkgver()...
==> Starting build()...
/startdir/PKGBUILD: line 36: ./scripts/build: No such file or directory
==> ERROR: A failure occurred in build().
    Aborting...

NobbZ commented on 2018-10-23 09:10 (UTC)

There is otf-fira-code available in community, can we have appropriate provides?

jzhu commented on 2018-07-01 23:02 (UTC)

@btd1337, I just did a fresh makepkg, but I can't reproduce your error. Also, I've glanced at the PKGBUILD, and there isn't a 'conflicts' field, so I'm very confused by the error.

Try re-fetching the PKGBUILD, perhaps, and that may solve your problem?

btd1337 commented on 2018-06-14 14:18 (UTC) (edited on 2018-06-14 14:18 (UTC) by btd1337)

-> Creating working copy of FiraCode git repo...

Cloning into 'FiraCode'...

done.

==> Starting pkgver()...

==> Sources are ready.

==> Cleaning up...

==> ERROR: conflicts contains invalid characters: ','

jzhu commented on 2016-08-08 12:51 (UTC) (edited on 2016-08-08 12:51 (UTC) by jzhu)

Fixed. Thanks, @jonathan!

jonathon commented on 2016-07-18 10:23 (UTC)

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

jzhu commented on 2015-12-25 19:25 (UTC)

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

1 2 Next › Last »