Package Details: ttf-nerd-fonts-input 1:3.1.1-3

Git Clone URL: (read-only, click to copy)
Package Base: ttf-nerd-fonts-input
Description: Fonts for Code, from Font Bureau, patched with nerd-fonts
Upstream URL:
Keywords: fonts input nerd ttf
Licenses: custom:Font Software License Agreement
Submitter: dangersalad
Maintainer: dangersalad
Last Packager: dangersalad
Votes: 1
Popularity: 0.000000
First Submitted: 2018-02-16 01:19 (UTC)
Last Updated: 2024-03-18 16:36 (UTC)

Latest Comments

1 2 Next › Last »

dangersalad commented on 2024-03-18 16:36 (UTC)

The checksum of the file seems to be changing every time it's downloaded now, so the check for that must be skipped in the PKGBUILD.

jfyne commented on 2023-05-31 11:52 (UTC)

The base url for the Input fonts has changed to

Nukesor commented on 2022-04-28 10:11 (UTC) (edited on 2022-04-28 10:12 (UTC) by Nukesor)

The shasum for seems to be no longer up-to-date.

==> Validating source files with sha256sums... ... FAILED
    v2.1.0.tar.gz ... Passed
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'ttf-nerd-fonts-input-1:2.1.0-2':
error: packages failed to build: ttf-nerd-fonts-input-1:2.1.0-2

Freso commented on 2021-03-30 01:53 (UTC)

You should rename v2.1.0.tar.gz into something unique, see

I’d suggest using "${_gitname}-${pkgver}.tar.gz::${pkgver}.tar.gz" like the nerd-fonts-complete PKGBUILD, so that you won’t be downloading the source twice if you build both…

dangersalad commented on 2020-12-08 18:46 (UTC)

@captn3m0 fixed that, turns out none of those dependencies were needed, leftovers from the original package I forked this from I suppose

captn3m0 commented on 2020-12-07 20:34 (UTC)

Broken because xorg-font-utils is not on AUR any more.

dangersalad commented on 2020-05-08 15:18 (UTC)

@alaskanarcher Noted about the package vs. build step. IIRC I just copied another PKGBUILD for another font and tweaked it.

I'll look into adding parallel to speed up the build

alaskanarcher commented on 2020-02-19 23:31 (UTC)

BTW I was reviewing the PKGBUILD. It seems that really the find step should be part of the build() function instead of package.

Also, find is very slow as it processes all glyphs/fonts serially. This package would build much faster if something like GNU parallel was used. See this SO question for some ideas about how to achieve this:

alaskanarcher commented on 2020-02-19 22:22 (UTC)

Any recommendations on speeding up build times?

alaskanarcher commented on 2020-02-19 21:47 (UTC)

@dangersalad the way to handle a dramatic change in version numbers is to use the epoch variable in the PKGBUILD. From man PKGBUILD

           Used to force the package to be seen as newer than any previous versions with a
           lower epoch, even if the version number would normally not trigger such an
           upgrade. This value is required to be a positive integer; the default value if
           left unspecified is 0. This is useful when the version numbering scheme of a
           package changes (or is alphanumeric), breaking normal version comparison logic.
           See pacman(8) for more information on version comparisons.