I have two suggestions for this package. I'd be happy make PR/MR or submit patches if they are deemed worthwhile.
Version string
Although this PGKBUILD contains a pkgver function that extracts a version string using "git describe --long" there is also a pkgver string with a hardcoded version that seems to override the version number. Would removing this hardcoded pkgver result in the value from the pkgver function being used?
Further to this, if the the pkgver function is used I have a suggested modification that would result in a version string that more closely matches the version string used by upstream (and returned by "river -version"). The only difference would be that a "-" in the upstream version is not permitted (man 5 PKGBUILD) and as such I guess would need to be striped or substituted for something else: eg "_".
This would have the added bonus of the package version number starting with 0.2.0 instead of 0.1.0 as it does now, which I think leads some users to think that the river-git package is actually older than the stable 0.1.3 release.
Desktop file
Note that upstream now distributes a river.desktop file which could be used in place of the one bundled in river-git.
Pinned Comments