setup-dev.sh pins stale dev-tool versions and downgrades newer local installs #590
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea#590
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
scripts/setup-dev.shinstalls the dev tools at hardcoded version pins, and several pins are now behind the latest release. Running the script over a newer local install downgrades it:Nothing flags a pin that has fallen behind, so the pins rot silently and the script quietly rolls a contributor's tools back over time. Downgrading a working toolchain is never the right fix.
Fix
Bump the pins to current, and add a drift check that flags a pinned dev tool that is behind its latest release, so the pins stay current and the script never installs a tool older than the one already present. Keep the pins for reproducibility; just keep them honest. This sits alongside the toolchain-currency theme in #526.
Acceptance
setup-dev.shmatches the current latest at the time of the change.setup-dev.shnever installs a tool older than the one already present.