| Age | Commit message (Collapse) | Author |
|---|
|
Instead use the `.g` prefix for commit hashes
similar to VCS packages: '0.12.0_dev.3433.g640acf862'
Although this commit changes the versioning scheme,
changing the epoch should not be needed since the format of the
primary version number and revision count remains the same.
This fixes an issue with '+' being a special character in URLs.
The build script now requires 'ripgrep' in order to rewrite versions.
I could have used python or jq but this is much more readable.
|
|
Arch Build System doesn't handle this.
Instead, everything is downloaded manually in prepare()
Avoid downloading version index twice in pkgver()
Minor refactoring for downloading version index
|
|
|
|
This continues to work without modification.
I am only bumping the version here because of the
minor version increase from 0.11 -> 0.12
To clarify once again, this is an auto-updated package which
should not require manual intervention for most updates.
The exception is the documentation, which currently seems to be broken?
|
|
Some people have been having trouble which I cannot reproduce.
Maybe this will somehow help reset things?
|
|
|
|
Thanks to @dithpri for suggesting this changes.
Update version to 0.11.0_dev.681+f02073434
|
|
Whoopsies
|
|
|
|
I see no reason for it to live. <evil laugh>
|
|
> Secondarily, while I appreciate that check really makes sure that Zig works, the way it's implemented currently litters the default Zig cache (located under $HOME by default) with build products. If I may suggest, isolating Zig to either not use a build cache at all or to keep it confined to the build environment would be preferrable.
> - @paulsnar (on AUR)
Luckily paulsnar fixed his own bug report, by emailing me a patch ;)
Unfortunately, there is no way to disable caching right now
(see zig issue #12317), so using a local cache is the best option.
Elaborated-by: Techcable <Techcable@techcable.net>
|
|
Zig doesn't consistently package documentation
across platforms or different builds.
See issue https://github.com/ziglang/zig/issues/9158
This has regressed and changed layout multiple times....
Thanks to @paulsnar for noticing this :)
Continuing changes like 9e02c353089ebce6dfb3734b78b90ef544956935 would
just lead to endless whack-a-mole.
|
|
This was caused by a bad .gitignore file which explicitly
included files (instead of it's usual role of excluding files).
Thanks to @legendary-cookie for noticing this.
Now I switched to the traditional form that excludes files (so this
specific git issue should not happen again).
Bump pkgver to indicate
|
|
|
|
|
|
It is not needed thanks to auto-updating
|
|
Apparently zig moved back to the old format?
Need to bump version in PKGBUILD (despite auto-update feature),
so that AUR registers the change in this script.
This reverts commit 3b8d78cc12b99ea597c4d5d9760a3a8abd7ca5b7.
|
|
The location in the nightly tarball moved.
|
|
Downloads directly from https://ziglang.org/download
GPG verification of downloaded files is not currently possible because Zig nightly binaries aren't signed.
See github issue https://github.com/ziglang/zig/issues/4945 for details
Using hardcoded sha256 is also impossible because this is an auto-updating package
Therefore, there is no security beyonnd the basic integrity of a https:// network connection (although that is still some security, you would have to forge a signed HTTPS certificate to intercept).
This commit also changes the versioning scheme to match
the upstream downloads (and be compatible with the main zig package)
This requires incrementing the "epoch"
This change also changes the package to supports multiple architectures (both x86_64 and ARM64)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|