For packages that pull from a VCS (hg, git etc.) the version number in the PKGBUILD corresponds to the last time the maintainer updated the PKGBUILD. This is often long ago, and the VCS upstream is usually updated since then, but apacman gives the warning e.g.
warning: pentadactyl-hg-7140.59c43695e9ee-1 is up to date -- reinstalling
Could we have apacman skip this version check if the PKGBUILD contains a pkgver(){ ... } function (indicative of a VCS package)? Note that it's not possible to get the true version number for VCS packages without actually cloning the VCS repo. Once the .tar.xz is built and control is handed over to pacman, the appropriate warning will be given anyway based on the actual version of the package that was built from VCS source.
For packages that pull from a VCS (hg, git etc.) the version number in the PKGBUILD corresponds to the last time the maintainer updated the PKGBUILD. This is often long ago, and the VCS upstream is usually updated since then, but apacman gives the warning e.g. warning: pentadactyl-hg-7140.59c43695e9ee-1 is up to date -- reinstalling
Could we have apacman skip this version check if the PKGBUILD contains a pkgver(){ ... } function (indicative of a VCS package)? Note that it's not possible to get the true version number for VCS packages without actually cloning the VCS repo. Once the .tar.xz is built and control is handed over to pacman, the appropriate warning will be given anyway based on the actual version of the package that was built from VCS source.