install.sh: idempotent upgrade (version-skip + clean reinstall) - #14
Merged
Merged
Conversation
- Resolve the release once, read its tag_name, and stamp it to $INSTALL_DIR/.release. Re-running now no-ops when already on the target tag (BASERT_FORCE=1 overrides). - Remove the previous bundle's artifacts before extracting so a file dropped in a newer release can't linger as an orphan (only known bundle paths are touched). - Document BASERT_FORCE.
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
1 participant
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.
Hardens the installer for re-runs on an already-installed system.
Changes
tag_name, and writes it to$INSTALL_DIR/.release. A re-run no-ops when you're already on that tag (basertpresent + stamp matches).BASERT_FORCE=1reinstalls anyway.basert,basert-*,baseRT_*,libbaseRT.dylib,baseRT.metallib,include/) — a customINSTALL_DIRwith unrelated files is safe.BASERT_FORCEdocumented.Verified:
sh -nclean; tag + asset URL parse correctly against the live release API (v0.1.3). PATH wiring is unchanged (already idempotent).