From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Guix beyond 1.0: =?utf-8?Q?let=E2=80=99s?= have a roadmap! Date: Tue, 09 Jul 2019 12:22:38 +0200 Message-ID: <87d0ijjymp.fsf@elephly.net> References: <877e97vws8.fsf@gnu.org> <87zhlz1aiq.fsf@roquette.mug.biscuolo.net> <504D1A97-2EBD-46A1-85B8-091C923DD6A1@vllmrt.net> <878stirsdc.fsf@gnu.org> <37B7DD8F-AC41-4001-80D7-C26DF0D2F024@vllmrt.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:470:142:3::10]:57924) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hknHX-0003l6-5v for guix-devel@gnu.org; Tue, 09 Jul 2019 06:23:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hknHV-0002JM-2S for guix-devel@gnu.org; Tue, 09 Jul 2019 06:23:31 -0400 In-reply-to: <37B7DD8F-AC41-4001-80D7-C26DF0D2F024@vllmrt.net> 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: rob@vllmrt.net Cc: guix-devel@gnu.org Hi Robert, >>> - more consistent and useful output =E2=80=94 currently it=E2=80=99s ve= ry easy to miss the >>> actual cause of an error between a lot of noise, e.g. all those =E2=80= =9Crecompiling >>> scheme module=E2=80=9D messages >> >> When do you see =E2=80=9Crecompiling=E2=80=9D messages? > > Here=E2=80=99s an example: ~/guix-postgrest$ guix build -L . postgrest > ;;; note: source file ./bytestring.scm > ;;; newer than compiled /gnu/store/r6w8vjfdii0pscbp6lmy6siqvzy2lgcn= -postgrest/lib/guile/2.2/site-ccache/bytestring.go > ;;; note: source file ./check.scm > ;;; newer than compiled /gnu/store/r6w8vjfdii0pscbp6lmy6siqvzy2lgcn= -postgrest/lib/guile/2.2/site-ccache/check.go This is certainly not normal. Why do you use =E2=80=9C-L .=E2=80=9D here? = I don=E2=80=99t think we recommend this anywhere in the manual. It does not look like a common use case. When we develop packages we do this from a git checkout where we compile modules with =E2=80=9Cmake=E2=80=9D to get rid of these messages. Having the messages is good, though, because interpreting these files instead of using the compiled variants comes with a massive drop in performance. Since users who don=E2=80=99t develop their own modules won= =E2=80=99t ever see these message I think it is a reasonable reminder to developers to compile their modules. > My reason for the suggestion is that my general impression is that error = messages > and useful console output is not a priority that=E2=80=99s generally agre= ed upon. It certainly is a priority as demonstrated by the full (but unfortunately failed) Outreachy internship project to overhaul console output, which was later picked up by me and later massively extended by Ludovic to hide build output by default, add spinners, colours, hints, etc. Any further work in that direction would be very welcome, though I=E2=80=99m afraid that the low-hanging fruit has already been plucked. -- Ricardo