Kirill A. Korinsky wrote: > On Tue, 20 Oct 2026 08:56:00 +0200, > David Uhden Collado <daviduhden@gmail.com> wrote: >> >> It adds git and xdg-utils as runtime dependencies, since Codex uses >> them for repository operations and opening browser links. >> > > Can you explain which "repository operations" require git? > > And how does it open browser links via xdg-open when it runs via SSH? Shall > I add chromium and firefox as run dependency by your logic? > Hello Kirill, Codex uses Git directly, not just through user commands. For example, codex-rs/git-utils/src/apply.rs invokes: git rev-parse --show-toplevel git apply --check git apply --3way It also uses Git for repository inspection and change tracking. These are normal development features, not unrelated utilities. Declaring Git as a runtime dependency ensures they are available without requiring users to install it separately. Regarding xdg-utils, Codex uses webbrowser::open() for authentication and opening links. On Unix, xdg-open is one of its supported browser launch mechanisms. SSH does not necessarily mean a headless environment. Codex can run locally, with X11 forwarding, or with a configured browser handler. xdg-open is only a dispatcher. It uses the user's configured browser and does not require installing Chromium or Firefox. I am not proposing either as a dependency. Neither Git nor xdg-open is required for every possible Codex operation, but both support existing functionality. My intention is to provide a functional package rather than leave these tools as undocumented requirements. Thanks, David.
No comments:
Post a Comment