Ability to point mason build client at custom scripts directory
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 258
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
Being able to point at a custom scripts directory would allow:
- Writing test packages, like in #378, without polluting the main `scripts/` directory.
- Remove the hack to created temporary testing scripts I added in https://github.com/mapbox/mason/blob/1319207a0e88eb842156ca027876be3770aca587/test/broken_package_must_error.sh#L14-L16
- Allow the mason client to be used, unmodified, to build packages that are versioned elsewhere.
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
Start by tracing how the mason client locates and uses the main `scripts/` directory. Inspect `test/broken_package_must_error.sh`, especially the temporary-script workaround referenced in the issue. Done means the client accepts a custom scripts directory, supports test or externally versioned packages, and no longer requires those scripts to be placed in the main directory.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100