8255ff90
ci: export the version instead of sed-ing a tracked APKBUILD
The version reaches abuild as $PKGVER now, and the tracked APKBUILD is never rewritten: Go reads vcs.modified from `git status --porcelain`, so a sed of a tracked file stamps every packaged binary dirty for the whole abuild run. The export alone would not have fixed it. .gitignore covered the intermediate web/static/main.css and not the content-hashed main.min.<sha>.css that `make css` renames it to — the file that survives, and that build() writes BEFORE go build — so every packaging run compiled with an untracked file in the tree. /src/, /pkg/ and /tmp/ are the three directories abuild works in inside this checkout, GOTMPDIR among them. Also: the cacher bootstrap splits into install + init so the installer's PATH export is sourced by the next task, and goes through install.sh for its checksum verification; scss collapses into the --exec miss-and-seed form; cache_restore takes --optional plus the half-restored module cache repair; cache_save moves after publish and drops the exists-guards; publish gates on a readable ~/.apk-ci.env; tags build. package() stages what build() produced (make install-files) instead of recompiling both binaries in a fresh fakeroot process with no cache pins, and stops installing static assets that //go:embed already put in the binary. The `[ -d ./cmd/... ]` skip guards are gone: a deleted cmd/ was a green build that packaged nothing. The reasoning lives in docs/ci.md, because the manifest is a varchar(16384) and a submission over the cap gets no CI at all.
Eugene Blikh <bigbes@gmail.com> — 2026-08-08 22:27:37 UTC
Commit 8255ff90741113fd85e6f15706127bb5c30ca3f5 —
view raw patch
Parent(s):
9b5827b6
| File | Status | + | − |
|---|---|---|---|
.build.yml
|
M | +83 | -40 |
.gitignore
|
M | +24 | -2 |
APKBUILD
|
M | +33 | -5 |
Makefile
|
M | +90 | -27 |
docs/ci.md
|
A | +247 |