Package Details: zig-dev-bin 20220712-1

Git Clone URL: https://aur.archlinux.org/zig-dev-bin.git (read-only, click to copy)
Package Base: zig-dev-bin
Description: A general-purpose programming language and toolchain for maintaining robust, optimal, and reusable software
Upstream URL: https://ziglang.org/
Licenses: MIT
Conflicts: zig
Provides: zig
Submitter: zhangkaizhao
Maintainer: zhangkaizhao
Last Packager: zhangkaizhao
Votes: 9
Popularity: 0.65
First Submitted: 2020-09-20 08:29 (UTC)
Last Updated: 2022-07-12 15:40 (UTC)

Dependencies (0)

Required by (42)

Sources (1)

Latest Comments

Techcable commented on 2022-08-05 05:55 (UTC) (edited on 2022-08-06 15:22 (UTC) by Techcable)

It would be nice if you added a custom pkgver() to allow automatically detecting new versions.

From the man page for PKGBUILD(5)

pkgver [...]

The pkgver variable can be automatically updated by providing a pkgver() function in the PKGBUILD that outputs the new package version. This is run after downloading and extracting the sources and running the prepare() function (if present), so it can use those files in determining the new pkgver. This is most useful when used with sources from version control systems (see below).

There is a good example of this on the ~~firefox-nightly~~ firefox-nightly-bin package

EDIT: Actually the firefox-nightly package builds from source, firefix-nightly-bin package has a good example of auto-updating binaries.

I am working on auto-updating dev binaries now. However, there is a serious problem: It is currently not possible to do GPG checking with auto-updated builds, since Zig tarballs are not GPG signed. It is not possible to do hardcoded sha256 checks (the approach used here) because auto-updates change the hash.

This means auto-updated builds would rely on a secure internet system, not cryptogrphy. I don't know what the AUR policy is here, do packages have to be GPG/SHA verified, or is just good practice?

cynik commented on 2022-04-04 07:34 (UTC)

How often do you update the package?

hannu commented on 2021-07-12 07:58 (UTC)

Stripping the binaries takes a long time and is unnecessary. Could you add OPTIONS+=(!strip) to the PKGBUILD?