Arch Linux User Repository

@blueyed

I'll recommend to you two possibilities:

1. The git history for this pkgbuild is always accessible, so just grab that last version and save it locally

2. Use the current version without a helper, manually shallow clone iosevka first, and set the pkgver value yourself, deleting the pkgver function.

@andykluger I see, but please consider keeping your changes. I might actually come back to using it when starting to customize the font myself. I'm storing it in ~/.cache already, but apart from the time it is also bad to have ~1GB there for a font. I've seen the discussions about shallow clones (e.g. https://www.reddit.com/r/archlinux/comments/3nz1r4/question_for_arch_devs_makepkg_and_git_why_not/).

@blueyed alright, in that case I'm actually going to revert most of the changes, as Arch team generally thinks this is a bad idea. If you're using AUR helpers and big repos, you might want to make sure the repos are stored in a persistent spot, so only the initial clone (and not subsequent updates) requires a big download.

And yes, Iosevka is life.

@andykluger Nice, have just seen the update.

I've switched to a variant patched with Ligaturizer (via https://github.com/be5invis/Iosevka/issues/248#issuecomment-414131620) though, to make it work with Kitty terminal.

It is a very nice font! (coming from Ubuntu Mono / Hack)

@blueyed

I've enforced a shallow checkout now

@blueyed

1. Yes, I think I'll update these to grab the master zip instead of a git checkout, thanks. I'm not sure how to properly get the revision info in that case, however.

2. Look at the private-build-plans.toml -- the termlig-custom package builds according to the configuration under [buildPlans.iosevka-termlig-custom] . You can copy this file to ~/.config/iosevka/ to modify it, and the pkgbuild will use that.

1. Given the size of the repo it would be useful to have a ttf-iosevka-custom package for the latest release, and/or ttf-iosevka-custom-git using the master tarball instead.

2. Do I understand it correctly that ttf-iosevka-termlig-custom-git is quite the same, but just defaults to building something else?

@mustaqim (and everyone) it's now updated to use the new build system, but no longer looks at that environment variable. For configuration, please copy the provided toml file to ~/.config/iosevka/ and modify from there.

The build method has changed, you need to change edit this into the PKGBUILD:

prepare() {
  cd "Iosevka"
  sed -i '/# Building plans/a [buildPlans.iosevka-custom]\nfamily = "Iosevka Custom"\ndesign = ['"$IOSEVKA_DESIGN"']\n' build-plans.toml
}

build() {
  cd "Iosevka"
  npm install
  npm run build -- contents:iosevka-custom
}

This will add:

[buildPlans.iosevka-custom]
family = "Iosevka Custom"
design = ["v-y-curly", "v-l-tailed", "v-g-opendoublestorey", "v-zero-dotted", "v-asterisk-low", "v-dollar-open", "v-numbersign-slanted", "v-underscore-low"]

to build-plans.toml.

You also need to set an ENV variable that is comma separated(eg. in fish):

set -gx IOSEVKA_DESIGN '"v-y-curly", "v-g-opendoublestorey", "v-zero-dotted", "v-asterisk-low", "v-dollar-open", "v-numbersign-slanted"'

@flying-sheep good idea, thanks, should work like that now.