Open soloturn opened 3 months ago
to triage, this should work
@Jguer the use case is special. the version is calculated from git repository, and is NOT the same as in the AUR PKGBUILD file, as i, as a package maintainer of cosmic-comp-git, do not update the version on every git commit in the upstream repository. but, the version is calculated out of the git hash of the upstream repository. this means, a version is installed, which is different from the one in the AUR.
the case failing is then, if one starts the install again, and the upstream git did NOT change. yay does NOT notice the version is already installed, and does download, compile, etc etc again.
Observing the same behavior for golden-cheetah-git since a few weeks: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=golden-cheetah-git
It reinstalls even if there are no new commits in the git repository, although it skips the rebuild.
can yay please notice that a package from git is already installed if the pkgver() function returns the same value of installed package? example, cosmic-comp-git.
and it would build again and install again. even if the prepare function returns the same version which is already installed: