mesonbuild / mesonbuild/wrapdb
Dependencies not updating with package update
Nobody has claimed this yet.
- Dominant language
- Meson
- Stars
- 118
- Forks
- 298
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 24
Description
For my wrap package, `kraken-engine`, I have sdl2 dependencies and a few other necessary ones. Whenever I put out a new version of my lib and install it with `meson wrap update ...`, all the old sdl2 packages stay and, because they're "from" the last version, re-configuring becomes a hiccup. The current solution is to just delete the entire `/subprojects` content first then reinstall my lib. Is there a better way to go about this that I didn't see in the docs, or is it just an unfortunate side-effect of a dependency with dependencies?
Contributor guide
No contributing guide indexed for this repository
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 examining the `meson wrap update ...` behavior described for the `kraken-engine` wrap and the contents of `/subprojects`; consult the relevant wrap documentation first. Done means establishing whether old `sdl2` dependencies should be removed during an update and documenting the supported update workflow or confirming the behavior as expected.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100