On Tue, 20 Oct 2026 12:57:00 +0200, David Uhden Collado <[email protected]> wrote: > > Your example confirms that the existing managed-release check works. > However, it only covers one update path. > > The patch also addresses: > > - "update --from-cli", which can copy and select a local CLI package. > - The background updater, which can be started independently. > - "codex update" and the TUI, which select update mechanisms based > on the detected installation method. > - Daemon startup, ensuring that no managed updater is launched. > > I agree that the current installation already rejects several of > these operations. The purpose is to enforce an explicit OpenBSD policy > rather than depend on upstream installation detection continuing to > behave the same way. > > It also improves diagnostics. Instead of a generic "unsupported" > status or a message about missing managed releases, users receive > a clear explanation that Codex is managed by OpenBSD packages and > must be updated with pkg_add -u, followed by a daemon restart.
~ $ codex update Error: Could not detect the Codex installation method. Please update manually: https://developers.openai.com/codex/cli/ ~ $ can you at least try behaviour of codex from ports before suggest that something doesn't work? -- wbr, Kirill
