Also my bad. The PKGBUILD uses a custom PATH with depot_tools, and I assumed that the which
command would use that PATH. It didn’t.
Building the package worked on my system because I set the PATH when building the package by hand, and for some reason, it never reverted.
And now it looks like just entering the expanded value of which
gives a completely different error that never showed up before. I’m just going to restore the old hack again. Maybe I should just use the depot_tools AUR package. Or maybe not, if that’s going to open a whole new can of worms.
Pinned Comments
ImperatorStorm commented on 2024-10-02 17:56 (UTC)
Remember: You are expected to have the
base-devel
metapackage installed before using the AUR.ImperatorStorm commented on 2022-08-06 04:31 (UTC)
A note that, per Aseprite's EULA, binaries created by this PKGBUILD CANNOT BE DISTRIBUTED.
I will comply with any upstream requests to remove this package.
ImperatorStorm commented on 2022-01-06 00:07 (UTC)
Big thanks to ISSOtm for rewriting the PKGBUILD!
ImperatorStorm commented on 2021-12-31 21:31 (UTC) (edited on 2022-01-03 04:42 (UTC) by ImperatorStorm)
Hosting this package's PKGBUILD at https://github.com/ImperatorStorm/PKGBUILDs