Hello, I'd like to start testing my PKGBUILD work with devtools prior to pushing my work to the AUR however I rely on packages based in the AUR for dependencies and when I try to use *extra-x86_64-build* in the location of the PKGBUILD it works for a bit but then fails because it can't resolve the AUR-based dependency packages. That makes sense as it's replicating the local *makepkg -s* process, which would also fail if I didn't have those dependencies installed ahead of time.
I normally accomplish this with yay <https://aur.archlinux.org/packages/yay> then build the PKGBUILD with *makepkg -s*. How do other AUR maintainers traditionally resolve their AUR-based dependencies when working with devtools? I'm not opposed to using yay with devtools if pulling in an AUR wrapper is appropriate; I'd just like to avoid having to manually install a bunch of dependencies by hand before I'm able to test if my PKGBUILD work is sound. Thanks!
