I doubt these are actually useful because you are supposed to build in a clean chroot environ tho...

I think you misunderstood something about building in a clean chroot.

Yes, PKGBUILDs should always be able to build in a clean chroot. This is to make sure no dependencies are missed, it can improve reproducibility if required and some compilation problems are mitigated.

Nowhere does this imply PKGBUILDs should always be built in a clean chroot. Using a fresh chroot for every package can extend download and packaging times, makepkg does not require it, and almost no AUR helpers automate this.

So I think the vast majority of users doesn't bother and this isn't wrong per se.

Thanks for adding the fix anyway!

@gwuensch Should be there after next release.

I doubt these are actually useful because you are supposed to build in a clean chroot environ tho...

Hi. Packaging currently fails with stale wheels in the srcdir.

Could you please either clean these up with a git clean -fdx in prepare(), as is suggested by the ArchWiki, or create a separate directory for each version (i.e., include $pkgver in the source directory's name)?