verify release binaries
Open
Nobody has claimed this yet.
build-ci
testing
- Dominant language
- Rust
- Stars
- 14
- Forks
- 2
- Avg merge
- 12h 42m
- Merged PRs (30d)
- 61
Description
Verify on genuinely clean machines. A fresh EC2 instance with nothing installed, and ideally a Mac that has never had your toolchain. ldd vxc (Linux) and otool -L vxc (macOS) will tell you exactly what you're still depending on.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the release vxc binary on a genuinely clean EC2 instance and, if available, a clean macOS machine. Run ldd vxc on Linux and otool -L vxc on macOS to identify remaining dependencies. Done means verifying that the binaries run without relying on preinstalled toolchains or undeclared libraries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100