Hi,
swedebu...@riseup.net skribis:
> I think the current logging is good enough.
>
> I vote for closing this as Brenton did not answer during a long time and
> nobody else thought this was worth implementing.
I agree, done!
Ludo’.
Hi
I think the current logging is good enough.
I vote for closing this as Brenton did not answer during a long time and
nobody else thought this was worth implementing.
We could add a note to the manual with a very general pipe output tip,
but it would probably just clutter an already large manu
Hi Brenton,
Brenton Horne skribis:
> As I understand it only the guix build command has an option to log output to
> a file.
Every derivation that is built, regardless of the command, has its log
stored in /var/log/guix/drvs. What ‘guix build’ has is a simple way to
get the file name or URL o
Brenton Horne writes:
> For example,
> `guix pull && guix package -u` has taken up to 12 hours to run for me
> before, so if it fails and doesn't log it can be quite an irritating waste
> of time and deter people from filing invaluable bug reports about issues
> they've experienced with guix.
“
This feature request isn't specific to guix build (it was low priority to
me as I knew it at least had the ability to log, thanks for telling me it
automatically does but it doesn't really change this feature request), it's
asking for all guix commands with substantial output to automatically log.
Brenton Horne writes:
> As I understand it only the guix build command has an option to log output
> to a file.
Actually, the output of “guix build” is indeed stored by default.
You can get it by asking for the logs for a given derivation.
For example:
# build something, please
guix b
I'm afraid I have no knowledge of Guile or Scheme. Looking at the Guile
manual seems to indicate to me it's a language quite unlike most languages
I've coded in. The only exception is that it does look a little like Emacs
Lisp.
On 26 May 2017 at 04:10, Arun Isaac wrote:
>
> Brenton Horne writes:
> I realize people can already log all output using redirection like
> with:
>
> COMMAND > output.log 2>&1
>
> but with this method no output is shown at the command-line so users can't
> track what guix is doing in real-time.
Somebody else should comment on the feature request. But, for immediat
Hi,
As I understand it only the guix build command has an option to log output
to a file. I would like to request that each guix command have the option
at least (if not automatic like it is for Gentoo's Portage package manager)
to log all output to a file. I believe this will help both users and
