Add support for local binary repository
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 258
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
Following the pattern of tools like [ivy repositories](http://ant.apache.org/ivy/history/latest-milestone/settings/resolvers.html), [apt-get PPA's](https://help.launchpad.net/Packaging/PPA), etc, `mason` should have the option to look for binaries in local directories, rather than only looking at GitHub/S3.
This would be useful when making multi-project changes (e.g. new feature in `mapnik`, requires updates to `node-mapnik` bindings, and then a change on Mapbox Studio), meaning that nothing special would need to be done as new code flows up the chain, it could be as simple as `mason publish --local` in the downstream project, then `mason install ` in the upstream project.
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 with the existing entry points for `mason publish` and `mason install`, and compare how GitHub and S3 repositories are currently selected. Done means a published binary can be placed in a local directory and a downstream project can install a specified local version using the demonstrated commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100