@jaltek Oh, looks like I never came across that guideline, I only read the PKGBUILD wiki page. I had no idea the replaces
field could be ignored in VCS packages. Now that I see it I think it makes sense though.
It also doesn't say anything about -git
packages having to pull from the last commit, and in fact even explains how to fix the source on a specific commit. But I found this section in the AUR wiki page that gives the impression that -git
packages are indeed meant to build from the latest.
Oh and now I also found this! (See the first point). AFAICT this package doesn't really patch or add anything that the official binary package doesn't do already, right? (except for RC versions, which are not the majority of versions) That means it's not complying with the first rule (unless I missed something or the RC versions do indeed work around that). Making it pull from the latest commit would effectively solve that.
And even if it turns out the package is fine, I'm pretty sure most people expect a -git
package to have the latest developments of the package. Maybe you should consider changing it so it does either way.
Pinned Comments