From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: =?utf-8?Q?What=E2=80=99s?= next? Date: Sat, 27 May 2017 12:01:00 +0200 Message-ID: <87zidyvctf.fsf@gnu.org> References: <877f16z9eo.fsf@gnu.org> <87y3tm8k2r.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44291) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dEYWx-0005Q1-Fh for guix-devel@gnu.org; Sat, 27 May 2017 06:01:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dEYWu-0007Fz-FT for guix-devel@gnu.org; Sat, 27 May 2017 06:01:07 -0400 In-Reply-To: <87y3tm8k2r.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 24 May 2017 15:23:40 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel Hello! Ricardo Wurmus skribis: > Here are some other annoyances: > > * the verbosity of reporting hash mismatches. You posted a neat little > change for that some time ago, but I cannot find it any more. Oh right, see attached. > * texlive. I=E2=80=99m working on splitting the package up. (An aggress= ive > firewall at work put a stop to that work, but I=E2=80=99ll try to resum= e very > soon.) Good point! Looking forward to that. > * very explicit but cryptic stack traces. I think that all errors > should be reported more nicely. The error can still be printed (on > demand?), but Guix probably should not spill its innards too readily. I agree with this direction, but we=E2=80=99ll have to work on concrete cas= es here. Bug reports of the form =E2=80=9Cwhen I do this I get a stack trace instead of an error message=E2=80=9D are welcome! Thanks, Ludo=E2=80=99.