Arch Linux User Repository

I added you as co-maintainer to the existing package mpz-git.

Well, I used to have mpz installed, and it is just inconvenient for users who, like me, have an daemon installed that notifies sometimes within minutes that a new version is out. It is inconvenient to fetch the PKGBUILD, check if there are more changes than a version bump + shasum change and than run makepkg on it. just running makepkg on a -git-package is much more convenient.

In terms of guidelines you may be allowed to do what you do, but I disagree to your consideration of stableness. How can a version be stable if it changes 15 times in one day (this is what happened 4 days ago)?

But maybe this should be discussed on aur-general mailing list.

Should I rename it to mpz-git? B/c it's kind of the whole point of CI. Besides, I consider every commit a stable release. Thus the pgrel - a number of commits since the last tag - a "stable" release on github. I couldn't find any rule (https://wiki.archlinux.org/index.php/AUR_submission_guidelines) that prohibits such scenarios, only circumstantial suggestions on reddit to use '-git' for bleeding edge packages. But again, I consider every commit stable at this moment. This package is not in community repo. But I'm willing to follow the rules if there are such rules

Please stop trying to upload every single commit to AUR. That is what -git packages are meant for.

Please rename the downloaded tarball to mpz-$pkgver.zip or so.

source=("$pkgname-$pkgver.zip::https://github.com/olegantonyan/mpz/archive/master.zip")