Skip to content

install: remove stale versioned dylibs on upgrade #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
prabod merged 1 commit into from
Sep 11, 2026
Merged

install: remove stale versioned dylibs on upgrade #63

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion install.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,8 +91,14 @@ curl -fSL --progress-bar "$url" -o "$tmp/bundle.tar.gz"
# (the bundle is flat: libbaseRT.{dylib,so}, baseRT.metallib on macOS, basert,
# basert-*, include/), so an unrelated file in a custom INSTALL_DIR is left alone.
mkdir -p "$INSTALL_DIR"
# libbaseRT*.dylib, not libbaseRT.dylib: since 0.2.4 the macOS bundle ships a
# VERSIONED library plus two symlinks (libbaseRT.0.2.4.dylib <- libbaseRT.0.dylib
# <- libbaseRT.dylib), and the bare name matched only the last of those. Every
# upgrade then left the previous release's real library behind — an orphan of
# the full binary size that nothing points at, and a loaded gun for any future
# change to the install name. (The .so pattern was already globbed.)
rm -f "$INSTALL_DIR"/basert "$INSTALL_DIR"/basert-* "$INSTALL_DIR"/baseRT_* \
"$INSTALL_DIR"/libbaseRT.dylib "$INSTALL_DIR"/libbaseRT.so* "$INSTALL_DIR"/baseRT.metallib
"$INSTALL_DIR"/libbaseRT*.dylib "$INSTALL_DIR"/libbaseRT.so* "$INSTALL_DIR"/baseRT.metallib
rm -rf "$INSTALL_DIR"/include

tar -xzf "$tmp/bundle.tar.gz" -C "$INSTALL_DIR"
Expand Down
Loading