|
| 1 | +# Arch Linux package |
| 2 | + |
| 3 | +Until CrewCode can be listed in the Arch User Repository (AUR), this repository |
| 4 | +ships a manual `crewcode-bin` PKGBUILD in [`packaging/arch`](../packaging/arch/). |
| 5 | +It downloads the official x86_64 Debian release artifact, verifies its SHA-256 |
| 6 | +checksum, and repackages its files as a native package managed by pacman. Arch |
| 7 | +does not install the Debian package directly. |
| 8 | + |
| 9 | +Only x86_64 is currently supported because CrewCode does not yet publish a Linux |
| 10 | +ARM64 artifact. |
| 11 | + |
| 12 | +## Install |
| 13 | + |
| 14 | +Install Arch's standard package-building tools if needed: |
| 15 | + |
| 16 | +```bash |
| 17 | +sudo pacman -S --needed base-devel git |
| 18 | +``` |
| 19 | + |
| 20 | +Clone CrewCode, inspect the package recipe, then build and install it: |
| 21 | + |
| 22 | +```bash |
| 23 | +git clone https://github.com/OnPoint-Dev-Tools/crewcode.git |
| 24 | +cd crewcode/packaging/arch |
| 25 | +less PKGBUILD |
| 26 | +makepkg -si |
| 27 | +``` |
| 28 | + |
| 29 | +`makepkg` downloads the pinned CrewCode release and refuses to build if its |
| 30 | +checksum does not match. `pacman` installs the resulting `crewcode-bin` package. |
| 31 | +Launch CrewCode from the desktop application menu or run: |
| 32 | + |
| 33 | +```bash |
| 34 | +crewcode |
| 35 | +``` |
| 36 | + |
| 37 | +Optional integrations such as an AI agent CLI must still be installed and |
| 38 | +authenticated separately. |
| 39 | + |
| 40 | +## Upgrade |
| 41 | + |
| 42 | +Pull a repository revision containing an updated PKGBUILD and rebuild it: |
| 43 | + |
| 44 | +```bash |
| 45 | +cd crewcode |
| 46 | +git pull --ff-only |
| 47 | +cd packaging/arch |
| 48 | +makepkg -si |
| 49 | +``` |
| 50 | + |
| 51 | +Until the package reaches AUR, AUR helpers cannot discover upgrades |
| 52 | +automatically. |
| 53 | + |
| 54 | +## Uninstall |
| 55 | + |
| 56 | +```bash |
| 57 | +sudo pacman -Rns crewcode-bin |
| 58 | +``` |
| 59 | + |
| 60 | +This removes application files managed by pacman. It does not remove the user's |
| 61 | +CrewCode configuration and data. |
| 62 | + |
| 63 | +## Maintainer release update |
| 64 | + |
| 65 | +After publishing a stable GitHub release with a matching |
| 66 | +`CrewCode-<version>-amd64.deb` artifact: |
| 67 | + |
| 68 | +1. Set `pkgver` to the release version and reset `pkgrel` to `1`. |
| 69 | +2. Replace `sha256sums_x86_64` with the artifact's SHA-256 checksum. Never use |
| 70 | + `SKIP` for a release binary. |
| 71 | +3. Regenerate metadata from `packaging/arch`: |
| 72 | + |
| 73 | + ```bash |
| 74 | + makepkg --printsrcinfo > .SRCINFO |
| 75 | + ``` |
| 76 | + |
| 77 | +4. Run `makepkg --cleanbuild`, install the result, and verify both the desktop |
| 78 | + launcher and `crewcode` command. |
| 79 | +5. If available, run `namcap PKGBUILD` and `namcap crewcode-bin-*.pkg.tar.zst` |
| 80 | + and review its findings before committing. |
| 81 | + |
| 82 | +When AUR account registration becomes available, the contents of |
| 83 | +`packaging/arch` can be pushed to the separate AUR Git repository for |
| 84 | +`crewcode-bin`. |
0 commit comments