Arch Linux User Repository

@bartus: Thank you for the patch. I've applied the fix about python-setuptools. Howver, I'm concerned about using pacman -Q in PKGBUILD. Instead, I created another package https://aur.archlinux.org/packages/pyalpm-next-git/ that tracks the 'next' branch of pyalpm and is compatible with pacman-git.

@yan12125: I've been using pacman-git for a few months now, and really starts missing features relaying on pyalpm (namcap,aurman). Are you stand by what you've told @eli-schwartz, or would you consider incorporating some slick patch to allow users build pyalpm-git with both pacman and pacman-git.

Here's my suggestion: [***]

Have no idea, how far we are form next pacman release, but last commit on git.archlinux.org/pacman.git says Prepare translations for next release, so perhaps sooner than later ;)

I'd like to keep the compatibility with the stable pacman. I remember the last time I installed pacman-git, many software broke as they worked with the stable pacman only. If there's a patch working for both pacman-git and pacman, I'm glad to add it into this package even if it's not merged upstream.

In order to work with pacman-git>=5.1.1.r103.ge9d91a68 the following backwards-incompatible patch is needed: https://lists.archlinux.org/pipermail/arch-projects/2019-January/005139.html

Don't know whether it makes sense to depend on pacman-git for this purpose though.

Thanks updated. Now pyalpm-git requires pacman>=5 or above, which is in [testing] only. Just skip updating pyalpm-git before pacman 5 hits [core]

please add this patch

https://lists.archlinux.org/pipermail/arch-projects/2016-January/004320.html

greetings

Thanks. Adopt and update.

Disowned. Feel free to update.

Also, please use `git describe --long --tags` instead of `git describe` in pkgver() as what [1] suggests.

[1] https://wiki.archlinux.org/index.php/VCS_package_guidelines

Please use provides=("pyalpm=$pkgver") so that it can be used with namcap, which requires pyalpm>=0.5