Support codex-app Linux layouts and version-safe backups#18
Draft
siraht wants to merge 2 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add installer compatibility for the community Linux packages from
am-will/codex-app, including the current ChatGPT-branded Codex payload, and keep theCodex++ rollback backup aligned with the app build being patched.
Changes
codex-desktopLinux install roots under/usr/lib,/opt,~/.local/opt, and~/.local/share.Codex,codex-desktop, andcodex.main-*.jsbeside a nested recovered entrypoint as well as the standard.vite/builddirectory.appBrandappears beforebuildFlavorin its options object.instead of creating an unsafe rollback point.
Why
The Linux port uses layouts such as:
Those layouts were not covered by the existing Linux locator. The current 26.707
ChatGPT/Codex payload also constructs window services with
appBrandbeforebuildFlavor, which caused installation to fail with:Separately, Codex++ uses one backup directory. Keeping the first-ever
app.asarindefinitely means that installing against a newer app can leave
uninstallpreparedto restore an unrelated old build. The new backup preparation step validates repeated
installs and retires the old set before backing up a fresh app build.
Validation
npm test npm run build git diff --checkThe test suite covers:
appBrandbeforebuildFlavorLive validation against a user-owned
am-will/codex-app26.707.31123 package completedinstallation, patched
.vite/build/early-bootstrap.js, flipped the Electron integrityfuse, and passed
codexplusplus statusandcodexplusplus doctor.