Silent option

[DRKV333]

I'm trying to use PKGBUILDer in a dockerfile to install some AUR packages. It would be nice, if PKGBUILDer had an option that makes it's output a bit less verbose.
Right now in my case, when makepkg gets invoked, it eventually calls make, which starts spewing out all the commands it's calling into stdout. This makes debugging the build process difficult.
The whole output from makepkg could be hidden. I believe pacaur has an option that does the same thing. In silent mode, pacman could also be run with --noprogressbar to make the logs look better.

[Kwpolska]

What kind of output do you expect, exactly? Can you provide a justification for your choices? Implementing a quiet mode is possible, but it’s hard to decide what should be included and what shouldn’t.

[DRKV333]

If makepkg completes successfully, I don't really care about anything it outputs. All I really want to know, is what packages are being installed from where, and if something fails, what was the error.

All of this will be run in an automated build on docker hub, so I'll only get to look at the output in the build log. This should be concise, so it's easier to read, but it should still contain enough information to figure out what the build did roughly. In case of any problems it would also be important to get some sort of meaningful error message, which is why I don't want to just >/dev/null the whole thing.

I'd say these considerations could also apply to pretty much any use case, where PKGBUILDer is used in some sort of automated script.