Mechanism to assert that all dependencies match
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 258
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
If package a depends on library b. And package c depends on both a and b we need to ensure that the version of b are exactly the same. @springmeyer and @kkaefer have discussed that this could be done roughly by:
- Encoding dependencies in mason.ini
- Clients reading mason ini could collect all versions encountered and throw as soon as a duplicate package is encountered that is not the same version as noticed before.
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
Read the existing mason.ini dependency encoding and the client path that reads it. Trace how dependency versions are collected, then define the conflict behavior when a package is encountered again with a different version. Done means mismatched versions are detected and rejected for the described transitive dependency case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100