From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brenton Horne Subject: bug#27067: Reply to Arun Isaac's reply Date: Fri, 26 May 2017 03:05:58 +1000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a114102b40f663505505c3c11" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33301) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dDwE7-0007P6-Ui for bug-guix@gnu.org; Thu, 25 May 2017 13:07:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dDwE2-000870-TB for bug-guix@gnu.org; Thu, 25 May 2017 13:07:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:35269) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dDwE2-00086u-PT for bug-guix@gnu.org; Thu, 25 May 2017 13:07:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dDwE2-0006dI-Jl for bug-guix@gnu.org; Thu, 25 May 2017 13:07:02 -0400 In-Reply-To: Sender: "Debbugs-submit" Resent-Message-ID: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 27067@debbugs.gnu.org --001a114102b40f663505505c3c11 Content-Type: text/plain; charset="UTF-8" Hi, Thanks. This feature would still be useful though, but your idea makes it less urgent. Automatic logging still sounds like a good idea as the Guix package manager is quite slow for some operations at the moment (not criticising the developers of Guix, after all at this early stage of development issues like this are to be expected), for me at least running GuixSD in a QEMU VM with 8 GB RAM and 3 CPU cores (3.3 GHz i7 cores), so it might save users interested in filing bug reports a lot of time (on re-running the problem command with `| tee output.log` after it) if the output was logged automatically. Saving users time will probably mean users will be far more motivated and able to provide bug reports on issues they experience, which is good for the entire Guix community as bugs would get reported and resolved faster. Thanks for your time, Brenton --001a114102b40f663505505c3c11 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

Thanks. This feature would still be useful though, but your idea makes i= t less urgent. Automatic logging still sounds like a good idea as the Guix = package manager is quite slow for some operations at the moment (not critic= ising=C2=A0the developers of Guix, after all at this early stage of develop= ment issues like this are to be expected), for me at least running GuixSD i= n a QEMU VM with 8 GB RAM and 3 CPU cores (3.3 GHz i7 cores), so it might s= ave users interested in filing bug reports a lot of time (on re-running the= problem command with `| tee output.log` after it) if the output was logged= automatically. Saving users time will probably mean users will be far more= motivated and able to provide bug reports on issues they experience, which= is good for the entire Guix community as bugs would get reported and resol= ved faster.

Thanks for your time,
Brenton
--001a114102b40f663505505c3c11--