Skip to content

Use measured TribesPad build space allowance - #208

Merged
chrissotraidis merged 1 commit into
mainfrom
codex/tribespad-measured-space
Oct 27, 2026
Merged

chrissotraidis merged 1 commit into
mainfrom
codex/tribespad-measured-space

Conversation

@chrissotraidis

@chrissotraidis chrissotraidis commented Oct 27, 2026 •

Copy link
Copy Markdown
Owner

TribesPad v0.2.0's 40 GB requirement was an inherited estimate. Fresh published-release player checks from PadMint main used 14.41 GiB for iOS and 12.96 GiB for macOS, including packaging and exported archives, with both games present.

Set the catalog allowance to 20 GiB, leaving 5.59 GiB above the larger observed footprint. Xcode and Homebrew prerequisites were already installed; retained builds for other targets or versions need additional space. TribesPad's README and recipe were merged in chrissotraidis/tribespad#32, and the published recipe and release notes now use the corrected allowance. Measurement record.

Validation: both scripts/player-check.sh tribespad ios - and scripts/player-check.sh tribespad macos - passed on Apple's Python 3.9.6. Neither backend fell back to Tribes 2 alone; the IPA contains Starsiege data and the Mac ZIP contains StarsiegeEngine. This is build evidence, with no new device or gameplay acceptance claim.

Local validation also passed: 493 unit tests (three skipped), manifest validation, and both release metadata audits. PadMint successfully read the updated, checksummed v0.2.0 recipe with disk_gb: 20.

@chrissotraidis
chrissotraidis merged commit 35c25d1 into main Oct 27, 2026
45 of 46 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant