void-linux / void-linux/void-packages
Package request: river-classic vs river (wayland compositor)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Package name
river-classic
Package homepage
https://codeberg.org/river/river
https://codeberg.org/river/river-classic
Description
The River wayland compositor is on v0.4.4 but void's river package is v0.3.7. I assume this is because there was a breaking change in the config format and general organisation of river to use the new protocol. The developer forked off the v0.3.x architecture to 'river classic'.
I'm not sure how void likes to handle this sort of migration. Perhaps a new river-classic package should be created and the river package could then track upstream.
Does the requested package meet the package requirements?
System
Is the requested package released?
Yes
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
Start by comparing Void's current river package with the river and river-classic upstream pages linked in the issue, including the stated v0.3.7 and v0.4.4 versions. Check how Void handles package splits after upstream breaking changes; the work is done when the appropriate package arrangement and version tracking are established.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100