feat(pkg): publish an installable package on every release - #6
Merged
Conversation
A release carried only the source zip GitHub attaches to any tag. This adds a PKGBUILD mirroring install.sh and folds the build into release-please.yml, so a release becomes something you can `pacman -U`. macarchy-install#17. Built locally on the target hardware and read back with tar -tf, not assumed: the binary, both units, the config template, licence and README. Three things carried over from the slice that proved this pattern (macarchy-install#16), each of which was a real failure there: The job hangs off release-please's own `release_created` output rather than a `release: [published]` trigger. release-please creates the Release with the default GITHUB_TOKEN, and GitHub raises no workflow run from a GITHUB_TOKEN event -- that trigger never fires and leaves no failed run to notice. pkgver is rewritten from the tag by the job, not maintained through release-please's extra-files, which cannot parse a PKGBUILD and stops release PRs being built at all. The shipped units say ExecStart=%h/.local/bin/… for install.sh's symlink. A package writes nothing into $HOME, so package() repoints them at /usr/bin and greps to confirm; verbatim they would give 203/EXEC from a package that installed perfectly. install.sh also seeds the config into ~/.config, which pacman cannot do: the example ships as a template under /usr/share and the scriptlet says how to take it and where to put the coordinates. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SYBhT1xfp3MQ1w3687F4Mp
26 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements part of macarchy/macarchy-install#17 (parent: macarchy/macarchy-install#14).
Second repo to get the pattern proven in macarchy/macarchy-touchbar#12.
What ships
Built locally on aarch64 Asahi and read back with
tar -tf.Carried over from the proving slice
release_createdoutput, notrelease: [published]— that trigger never fires, because release-please creates the Release withGITHUB_TOKENand GitHub raises no run from aGITHUB_TOKENevent.pkgveris rewritten from the tag by the job, not viaextra-files, which cannot parse a PKGBUILD and stops release PRs being built at all.%h/, with agrepto confirm — verbatim they give 203/EXEC.Suite: 42 passed.
🤖 Generated with Claude Code
https://claude.ai/code/session_01SYBhT1xfp3MQ1w3687F4Mp