Provide mechanism for junctioned plugins to express their dependencies
Open
- Dominant language
- Python
- Stars
- 140
- Forks
- 45
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
As discussed in https://gitlab.com/BuildStream/bst-plugins-experimental/-/issues/59, junctioned plugins currently cannot express which packages they need let alone which versions of said packages they need. BuildStream and plugins should agree upon API/metadata for providing this information so BuildStream can gracefully error out when plugin dependencies are unsatisfied.
Contributor guide
Research direction
Start by reading the linked BuildStream plugins discussion about junctioned plugin dependencies and compare it with the issue's requested behavior. Done means BuildStream and plugins have an agreed API or metadata format for declaring required packages and versions, with graceful errors when dependencies are unsatisfied.
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
- Needs clarification
- Newbie friendliness
- 20/100