On Tue, 13 Oct 2026 21:59:00 +0200, David Uhden Collado <[email protected]> wrote: > > You're right. The previous diff included more than the daemon > integration, and I should have made that clearer. Sorry for the > confusion. >
You did it again. > I've attached a revised diff against the current CVS tree, including the > previously missing patch files. > > The daemon integration itself is relatively small. It reuses the > existing Codex executable as the app-server daemon, installs it with the > required package manifest under libexec/codex, and makes the daemon > resolver use that executable instead of downloading or copying another > one into ~/.codex/packages. > > The existing upstream process management, Unix sockets, IPC, and > start/stop/restart functionality remain unchanged. Only internal > installation and self-update mechanisms are disabled, since pkg_add owns > the executable. Why do we need that daemon on the first place? I not sure that this is sane wrokflow: > + codex app-server daemon start > + codex app-server daemon version > + codex app-server daemon restart > + codex app-server daemon stop What a use case do you have for that daemon? > - Enable OpenBSD support in the WASM interpreter platform checks. > - Use MAP_STACK for the usable WASM stack region while preserving its > guard pages. Does codex use wasm? really? -- wbr, Kirill
