mason cache-clear command
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 258
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
There is a ./mason remove <package> <version> command that un-installs a package from mason_packages/<platform>/<package name>/<version>/. However if you remove a package and then re-install it you will get the same identical package from the cache at ./mason_packages/.binaries (instead of downloading the version from remote).
This ticket stands to remind us to:
- document this behavior
- consider adding a command to make this cache clearing easier (to avoid having to
rm -rf ./mason_packages/.binaries/....
/cc @allieoop
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 the ./mason remove <package> <version> command and the mason_packages/.binaries cache behavior described in the issue. Clarify whether the intended outcome is documentation, a cache-clearing command, or both; done means the chosen scope is explicit and users can clear or understand cached packages without manually using rm -rf.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100