Specifying build path with 4.0

[swilde]

I used to use --build argument with -A to specify the build directory where AUR packages are build and --builduser to set a specific user to build. In 4.0 these options seem to be gone. What is the correct way to emulate the previous behavior?

[fosskers]

Hi, thanks for the report. --build seems to have been overlooked - I will restore it for you tomorrow. In the meantime, you can set the build path in config. See here for how to do that. Also consult this page for how package building looks now. Mostly it's advice to not call sudo yourself.

As for the build user, packages are now built as your existing user, not through sudo-hacks as before, so I'm tempted to say you might not need --builduser anymore, but perhaps you have a unique usecase?

[fosskers]

packages verify OpenPGP (gpg) signatures during the build process.

For my own reference, can you name such a package so I can check its PKGBUILD?

[fosskers]

I just pushed a commit that restores --builduser.

[swilde]

Thanks a lot, I'll test it asap.
In the meantime: the package I last encountered with OpenPGP signitatur checking from aur is python2, but there are more for sure. Also I became aware of more times where the build user needs a writeable home: packages compiling golang might want to write $HOME/.cache, and then there is haskell which writes $HOME/.cargos as aura-git for instance ... So thanks a lot for resorting --builduser!
(btw, I created a build directory owned by nobody to use --build with the previous version)

[swilde]

I gave --builduser a spin and it seems to work as expected. I'm very greatful for your great support!

[fosskers]

Good to know that there are packages that won't want to build cleanly as root. The nobody workaround is just that, a workaround, and power users can use --builduser, etc., as necessary.

[swilde]

I successfully tested that --build works again as expected. Thanks.