1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
|
# Deploying the `cs` / `search_code` binary to the Artix (s6) cyberdeck
## TL;DR
The `search_code` agent tool shells out to a `cs` (code spelunker) binary. This
feature provisions that binary on **two** deployment paths automatically:
| Path | Mechanism | `cs` ends up at |
| --- | --- | --- |
| `bin/up` | Docker (`Dockerfile` / `Dockerfile.dev`, `cs-builder` stage) | `/usr/local/bin/cs` |
| `bin/service install` | native Arch package `code-search` (built by `packaging/PKGBUILD`, installed by `bin/install-pkg`) | `/usr/bin/cs` |
There is a **third** path — the Artix cyberdeck box — that is deployed by a
personal script living **outside this repo**
(`~/projects/cyberdeck/sync-dispatch.sh`). That script is not updated by this
feature and **must be edited once** (4 small additions) so the Artix box also
gets `cs`. Until then, `search_code` on the cyberdeck will return its graceful
`Error: search_code requires the 'cs' binary ...` message on every call.
This file documents that required follow-up. It is committed so the change isn't
forgotten; the actual edit happens in the cyberdeck repo, not here.
---
## Why this is needed
`packaging/PKGBUILD` now builds a `code-search` split package (a patched,
statically-linked `cs` pinned to upstream commit
`697e0bf194bbc7a4a877e5170c70618989fc92e7`, tag `v3.1.0`, plus
`docker/cs/luau-declarations.patch` for Roblox `.luau` declaration support). It
installs `cs` to `/usr/bin/cs`.
`code-search` is a plain static binary with **no init-system coupling**, so it
installs and runs identically on Artix (Arch-based, `pacman`/`x86_64`). The only
gap is that `sync-dispatch.sh` — which pushes packages to the Artix box and
`pacman -U`s them — has a hardcoded two-package list (`dispatch` + `dispatch-s6`)
and does not yet include `code-search`.
> Note: `sync-dispatch.sh` builds and pushes packages from the **main** dispatch
> checkout (`/home/tradam/projects/dispatch/packaging`), so this edit only
> becomes meaningful **after this feature branch is merged to `dev`** and that
> checkout rebuilds packages (`bin/build-pkg` / `sync-dispatch.sh --build`).
---
## The required edit to `~/projects/cyberdeck/sync-dispatch.sh`
Four small additions. After applying them, run `sync-dispatch.sh --build` (the
`--build` flag rebuilds the packages first, producing the new
`code-search-*.pkg.tar.zst`).
### 1. Declare the package name (next to `PKG_DISPATCH` / `PKG_S6`)
```sh
PKG_DISPATCH="dispatch-0.0.1-1-x86_64.pkg.tar.zst"
PKG_S6="dispatch-s6-0.0.1-1-x86_64.pkg.tar.zst"
PKG_CS="code-search-0.0.1-1-x86_64.pkg.tar.zst" # <-- add
```
### 2. Add it to the "package exists" pre-check loop
```sh
for pkg in "$PKG_DISPATCH" "$PKG_S6" "$PKG_CS"; do # <-- add "$PKG_CS"
if [ ! -f "${PKG_DIR}/${pkg}" ]; then
echo "ERROR: ${PKG_DIR}/${pkg} not found. Run with --build or 'bin/build-pkg' first." >&2
exit 1
fi
done
```
### 3. Add it to the `scp` upload
```sh
scp -q "${PKG_DIR}/${PKG_DISPATCH}" "${PKG_DIR}/${PKG_S6}" "${PKG_DIR}/${PKG_CS}" "${TARGET}:/tmp/"
# ^^^^^^^^^^^^^^^^^^^^^^^ add
```
### 4. Add it to the remote `pacman -U` and cleanup `rm`
Inside the remote script heredoc:
```sh
pacman -U --noconfirm "/tmp/$PKG_DISPATCH" "/tmp/$PKG_S6" "/tmp/$PKG_CS"
rm -f "/tmp/$PKG_DISPATCH" "/tmp/$PKG_S6" "/tmp/$PKG_CS"
```
> The remote script is generated inside `sync-dispatch.sh` and references
> `$PKG_CS` via the same variable-expansion mechanism already used for
> `$PKG_DISPATCH` / `$PKG_S6`. Make sure `PKG_CS` is exported/substituted into
> the remote script the same way those two are (search the script for every
> place `PKG_S6` appears and mirror it for `PKG_CS`).
No s6 service changes are needed — `code-search` ships only a binary, not a
service, so the existing `s6 repository sync` / `s6 set enable` dance is
unaffected.
---
## Verifying on the Artix box after sync
```sh
cs --version # -> cs version 3.1.0
which cs # -> /usr/bin/cs
pacman -Q code-search # -> code-search 0.0.1-1
```
Then, in a Dispatch tab with the `search_code` permission enabled, run a search;
it should return ranked results instead of the "cs binary not found" error.
For a `.luau` sanity check (confirms the Luau patch is present), search a Roblox
project with `only: "declarations"` — `function` / `type` / `export type` lines
should be detected.
---
## If you ever decouple `cs` from this repo
`code-search` is intentionally a standalone package (own name, own
`/usr/bin/cs`, upstream MIT license shipped). If `cs` later graduates to its own
AUR/repo package, the cleaner end state is to drop `package_code-search()` from
`packaging/PKGBUILD` and instead declare a `depends=('code-search')` (or the AUR
name) on the `dispatch` package — but as of this writing **no official or AUR
package for boyter/cs exists** (the AUR `cs` is an unrelated `ls`-with-icons
tool), so building it here is the correct approach.
|
