verbose backtraces when “invoke” fails

verbose backtraces when “invoke” fails

[Ricardo Wurmus]

Hi Guix,

I’d like us to catch the errors raised by “invoke”, so that the output
of a failing build looks nicer again.

Before we used “invoke” build phases evaluating to #f would cause the
build system to abort and print a nice message.  Now users get an ugly
backtrace that is much too verbose for what it’s trying to say, namely
that a command invocation failed.

There is no value in the backtrace itself (users don’t care where
“invoke” is defined, for example); we only want the error message.
Shall we fix this on core-updates?

--
Ricardo

Re: verbose backtraces when “invoke” fails

[Hartmut Goebel]

Am 21.01.19 um 09:21 schrieb Ricardo Wurmus:
> I’d like us to catch the errors raised by “invoke”, so that the output
> of a failing build looks nicer again.
+1

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

Re: verbose backtraces when “invoke” fails

[Ludovic Courtès]

Hi,

Ricardo Wurmus <rekado@elephly.net> skribis:

> I’d like us to catch the errors raised by “invoke”, so that the output
> of a failing build looks nicer again.

Yes, please!  That can be done in ‘gnu-build’ in (guix build
gnu-build-system).

Ludo’.