gprconfig kb not installed outside of bootstrap script
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- build-system
Research direction
Start with bootstrap.sh and the code or packaging rules that populate /usr/share/gprconfig. Check how release updates install the gprconfig knowledge base without bootstrapping a new architecture. Done means the knowledge base is installed through the normal update or packaging path, with the relevant installation behavior verified.
Written by the indexing model from the issue text.
Description
Since de15c785678e51ee586f643091f1fff303e3812d /usr/share/gprconfig is populated from within bootstrap.sh script only.
This is a problem for packaging/distributions because bootstrap.sh is not used for update between releases but only for bootstrapping on new architecture.
- Dominant language
- Ada
- Stars
- 82
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 AdaCore/gprbuild
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Prefer not operatorOpen
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in AdaCore/gprbuild
Similar issues
-
dependencies effort:S priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
app:web meta:ops
Difficulty 2/5 Half a day Newbie friendliness 78/100
osu-tournament-rating/otr#1113 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
bug cli libc sev-3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100