Resolve min-version in project.conf across internal junctions and suggest to update it
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system
Research direction
Start by tracing how project.conf reads min-version and how internal junctions are loaded and version requirements are checked. Confirm the behavior when a junction requires a higher version, then add coverage and ensure bst warns or errors clearly when the project's declared min-version must be updated.
Written by the indexing model from the issue text.
Description
Currently, if project.conf has a min-version: 2.3 (say) and some internal junctions of plugins:
name: foobar
min-version: 2.3
element-path: elements
junctions:
- plugins/buildstream-plugins.bst
If plugins/buildstream-plugins.bst is updated to a version that requires higher min-version than that the project itself specifies in project.conf, bst does not suggest or warn that min-version: 2.3 needs to be updated, but it should.
If the junction plugins start asking for a higher min-version then that effectively becomes the min-version of the project.conf, otherwise the project can be loaded.
Showing a warning or an error in this case would help people make a conscious decision of when/how to update internal junctions.
- Dominant language
- Python
- Stars
- 144
- Forks
- 45
- Avg merge
- 20h 38m
- Merged PRs (30d)
- 6
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.
More from apache/buildstream
-
logging
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/buildstream#2150 · 3 comments ·
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
apache/buildstream#2143 · 2 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/buildstream#2194 ·
-
Modification time of an element with an open workspace propagates into consumer element's sandbox Openbug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
apache/buildstream#2186 · 2 comments · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/buildstream#2184 · 1 comment ·
All issues in apache/buildstream
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/sig-end-user#406 ·
-
bug ci good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100