building aur fail which is caused by file extension name about docker-arch-build-aur HOT 5 CLOSED

Good catch, thanks!

from docker-arch-build-aur.

I went for a hopefully future-proof approach, let me know if you still experience any issues!

from docker-arch-build-aur.

The . after tar prevents using no compression at all.

I also noticed a related problem that is caused by the asterisks for moving the package. For example the AUR package zoom downloads an archive and calls it "${pkgname}-${pkgver}_orig_x86_64.pkg.tar.xz". After building the package (which basically repackages the archive) one is left with two archives called zoom-5.2.458699.0906-1-x86_64.pkg.tar.xz and zoom-5.2.458699.0906_orig_x86_64.pkg.tar.xz. Since both match the pattern, they will both be moved to the target directory. This isn't too bad, but not perfect either.

A possible solution I can think of is using PKGDEST from makepkg.conf. Since the makepkg user will probably have no write access to the /pkg directory, the directory cannot be specified directly using the variable. But one could specify a temporary empty directory. After building the packages that directory should only contain the package file, which means all files in that directory can be moved to /pkg, simplifying the glob pattern for moving the package further and avoiding problems with the file extension.

from docker-arch-build-aur.

Sounds good, would you be able to submit a PR? I don't want to over-complicate the scripts but your proposal sounds like it could be just one or two extra lines, so why not 😉

from docker-arch-build-aur.

Sure, i will give it a shot.

from docker-arch-build-aur.