Arch Linux User Repository

@andykluger It's because I use yay, perhaps I'm the only yay user of this package. I think it would be better not to check since I doubt there are any security implications for that.

@E it sounds like you are first overwriting that file yourself. It will work if instead you keep your custom file in the mentioned folder, and run makepkg from the clean, checked-out state of this repo.

However, if everyone still wants me to stop checking the integrity of this repo's file, I will.

But after the hash check, it will overwrite the shipped copy with one from ~/.config/iosevka/ if it exists.

For me I can't install it without editing the PKGBUILD because it will complain that my private-build-plans.toml fails validation.

If anyone else hates the new capital G with the "tooth" at the lower right, I've reverted that change at https://github.com/AndydeCleyre/Iosevka/tree/feature/toothless-G . I hope the old G comes back as a selectable glyph variant upstream, but no news on that yet.

If there's any interest here in my including this change as a patch, either enabled or disabled (commented out in the PKGBUILD) by default, let me know.

Well it does ship with that file, so the hash is known anyway. But after the hash check, it will overwrite the shipped copy with one from ~/.config/iosevka/ if it exists.

Why check the hash of the private-build-plans.toml? I thought the point of this package was to allow installers to set their own options with their own private-build-plans.toml.

@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)