Improve separation between build and install
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 258
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
Currently, if a binary package is not available, Mason tries to build the package from source. However, the system may not be set up to actually compile that package. Instead, we should make a clearer distinction between _using_ a library and _building_ a library.
Contributor guide
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
The issue names no files, tests, or entry points. Start by tracing Mason's fallback from binary installation to source compilation, then define separate use and build paths; it is done when a missing binary no longer triggers compilation unless building is explicitly requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100