On Wed, Sep 21, 2011 at 01:40:41AM -0400, Eric Bélanger wrote:
On Tue, Sep 20, 2011 at 11:40 PM, Allan McRae <allan@archlinux.org> wrote:
On 21/09/11 09:49, Dan McGee wrote:
On Tue, Sep 20, 2011 at 9:11 AM, Florian Pritz<bluewind@xinu.at> wrote:
This might help to locate a failing command which causes makepkg to abort.
Signed-off-by: Florian Pritz<bluewind@xinu.at> --- This is a request for comments and not a final patch. It's only been tested shortly. I just want to know if people like the idea.
I'm a +0 on this- mainly because I don't build enough to know whether people would find this helpful. People that package more than I, please speak up.
I'm also +0, but that might be because I am quite familiar with the packaging process and find where errors occur somewhat obvious.
Same here. For the few cases where it's not obvious, it's quite easy to pin-point the problematic line with some echo or 'return 1' statement.
And same here. I actually never really had the problem of not knowing where some build error originates from. It is kind of obvious in most cases and the error messages are often helpful enough. In case of doubt, you can always add "set -x" to the build() and package() functions manually as well.