At the current version, makepkg preserves the (non-local) variables that are declared in prepare() function. In this manner, you can declare global variables in prepare() and reuse them in pkgver() and build().
But it seems that pacaur destroys the (non-local) variables that are declared in prepare(). As a result, packages that uses this benefit, like mupen64plus-git will fail to build with pacaur, but will build fine with makepkg. In this way, pacaur seems to have an unmatched behavior compared to makepkg.
There is a user comment in the mentioned package page reporting a build issue with pacaur.
Output
$ pacaur -S mupen64plus-git
...
:: Installing mupen64plus-git package(s)...
:: mupen64plus-git package(s) failed to install.
:: ensure package version does not mismatch between .SRCINFO and PKGBUILD
:: ensure package name has a VCS suffix if this is a devel package
Version
Description
At the current version,
makepkg
preserves the (non-local) variables that are declared in prepare() function. In this manner, you can declare global variables in prepare() and reuse them in pkgver() and build().But it seems that
pacaur
destroys the (non-local) variables that are declared in prepare(). As a result, packages that uses this benefit, like mupen64plus-git will fail to build withpacaur
, but will build fine withmakepkg
. In this way,pacaur
seems to have an unmatched behavior compared tomakepkg
.There is a user comment in the mentioned package page reporting a build issue with
pacaur
.Output