Den 31-07-2016 kl. 04:22 skrev Eli Schwartz via aur-general:
*-hg/*-git/*-svn packages do not mean the source was checked out using those protocols, they mean that the package builds from the latest development sources and that therefore the PKGBUILD will automatically build e.g. the latest revision (or the latest revision of a particular development branch, depending on your scenario).
Unless you actually mean to indicate that that package fundamentally builds the development version from hg "tip", please use the version tarballs available at https://bitbucket.org/${user}/${repo}/get/${revision}.tar.gz
In this case, there do not appear to be tags, so just go with the latest commit hash. But still, it is false to claim that it is a development version. I don't know how you would go about calculating the actual pkgver though, if the repository doesn't seem to have tagged releases or proper versioning.
https://wiki.archlinux.org/index.php/VCS_package_guidelines#Mercurial has a recommended way/example of how to go about exactly this. I don't see a reason why this version string wouldn't be okay to use/mirror for a non-"-hg" package too, if there's not otherwise a good versioning scheme in place. This would also allow package versions to be directly comparable if a -hg package should emerge at a later point. -- Namasté, Frederik “Freso” S. Olesen <https://freso.dk/> AUR: https://aur.archlinux.org/account/Freso Wiki: https://wiki.archlinux.org/index.php/User:Freso -- Namasté, Frederik “Freso” S. Olesen <https://freso.dk/> AUR: https://aur.archlinux.org/account/Freso Wiki: https://wiki.archlinux.org/index.php/User:Freso