I assume you've just ran the local -a
command in some shell in some terminal. You could add the command within the PKGBUILD's check()
function and also echo the environment variables. This way you would see whether it is setup as expected also in the build environment. (An AUR helper or makepkg
might mess-up something here, e.g. makepkg
generally sets environment variables from /etc/makepkg.conf
.)
at the beginning
I've noticed that setting variables at the beginning of the file might not be reliable, at least that's my experience when using makechrootpkg
(see https://github.com/hipersayanX/ArchPackages/commit/1e61856d067b5aeae6828e39e01d617661b1069e). Hence I recommend to set environment variables within the relevant functions.
Pinned Comments
Martchus commented on 2016-10-31 11:39 (UTC) (edited on 2024-03-06 16:44 (UTC) by Martchus)
All my packages are managed at GitHub where you can also contribute directly: https://github.com/Martchus/PKGBUILDs
There also exist a binary repository: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#ownstuff
The packages within the binary repository are built against the latest packages from Arch Linux and hence might not be compatible with Manjaro. This can be the cause when the Plasmoid doesn't work.
Important remarks:
pkgrel
of the AUR package when a rebuild is required (only in accordance with Arch Linux of course, not in accordance with Manjaro).syncthingtray
broken until it has been rebuilt) or to uninstallsyncthingtray
temporarily before the update. After the updatesyncthingtray
can be rebuilt and reinstalled again.makechrootpkg
which is also how official developers build their packages (and how packages in my binary repository are built).c++utilities
,qtutilities
,qtforkawesome
andsyncthingtray
in that order.syncthingtray-qt6
instead of this package.makepkg --nocheck
ormakechrootpkg -- --nocheck
. It makes still sense to report failures. But please include the actual error message and not just the last few lines.