unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andrei Osipov <andrspv@gmail.com>
Cc: 19772@debbugs.gnu.org
Subject: bug#19772: Verbosity of guix build output
Date: Mon, 09 Feb 2015 22:17:44 +0100	[thread overview]
Message-ID: <87sieebx8n.fsf@gnu.org> (raw)
In-Reply-To: <87twyvnjvh.fsf@gmail.com> (Andrei Osipov's message of "Mon, 09 Feb 2015 19:13:22 +0300")

Please keep 19772@debbugs.gnu.org Cc’d.

Andrei Osipov <andrspv@gmail.com> skribis:

>> Just to be clear, I suppose you don’t just want something equivalent to:
>>   guix build foo > /dev/null
>> right?
>
> Yes. As I can see the output belongs either to ./configure, make, etc. or to
> guix itself. Only the guix output is desirable, the rest is mosly
> garbage.  

OK.  What exactly do you consider “guix output”?  I’m asking because
from the daemon’s viewpoint, everything is build output basically.

>> So would you like to get rid of all the build output except the “build
>> trace” lines
>
> Yes, but it still might be usefull to take a look at this build output,
> for example, to review configure options or results of make test.
> Might be the build output should be kept in some conventional location
> the way some utilities like perlbrew do that. 

That’s already the case, see ‘guix build --log-file’.

Ludo’.

  parent reply	other threads:[~2015-02-09 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 16:00 bug#19772: Verbosity of guix build output Andrei Osipov
2015-02-07 17:52 ` Ludovic Courtès
     [not found]   ` <87twyvnjvh.fsf@gmail.com>
2015-02-09 21:17     ` Ludovic Courtès [this message]
2016-03-08 22:34 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sieebx8n.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=19772@debbugs.gnu.org \
    --cc=andrspv@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).