2 Jul
2013
2 Jul
'13
8:05 p.m.
On 07/02/2013 09:55 PM, Dave Reisner wrote: > On Tue, Jul 02, 2013 at 09:40:13PM +0200, Alain Kalker wrote: >> For debugging PKGBUILDs, and for reporting build failures upstream, >> it is very important to know the exact commands that are executed >> leading up to a problem. >> By using `set -x` and an appropriate value for PS4, commands are >> logged before they are executed. > If you want to report build failures upstream, then building via makepkg > is already wrong. Not if: - the build failure is caused by an Autoconf bug (see FS#35983 - [libxcb] Build failure: .../install-sh: No such file or directory) - the package is built as vanilla, as possible, as is supposedly the Arch Way. - the logged commands fully reflect the build process, i.e. no interference from outside environment variables, etc. > > -1 on this. Please don't NAK just because you disagree on one possible use of this feature! As I've stated clearly, the patch has other obvious benefits: debugging PKGBUILDs. Thank you.