Please use an enhanced pkgver() implementation (like the one here).
Because you need to make sure that a tag with a suffix like -RC1 won't get converted to something like 2.2.0.RC1.r*, but result in the text suffix get joined directly to the end of the last digit (like 2.2.0rc1.r*).
Without this fix, text-suffixed tags like those with -RC will always be considered newer by pacman and build tools than the next stable tag.
E.g, current 2.2.0.RC1.r* is newer than the future stable release of 2.2.0.r*.
Pacman follows basically the same version comparison logic as Python's packaging tools do (based on the PEP 440 standard).
Can you please add provides and conflicts with librdkafka?
Please update to current version v0.11.1
https://github.com/edenhill/librdkafka/releases/tag/v0.11.1
Updating the dependency to `python` seems to be the correct solution. It seems some their scripts are in Python 2 format though.
Hi again. `makepkg` does not build without dependency to `python` (not `python2`). Please note I don't know enough about this package to tell what upstream expects by `/usr/bin/env python`: is it Python 2 or Python 3? Most of the Python scripts are tests, one is for packaging. Only one script remains and it looks like Python 3.
Thanks, updated the info.
Hi! `python` is a compulsory build dependency for this package.
Hi!
You might be interested in checking out https://aur.archlinux.org/packages/kafkacat-git which I just submitted and depends on librdkafka-git.