From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:46113) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1imytX-0005MU-Mq for guix-patches@gnu.org; Thu, 02 Jan 2020 06:44:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1imytW-0000xH-LS for guix-patches@gnu.org; Thu, 02 Jan 2020 06:44:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:60590) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1imytW-0000x9-I2 for guix-patches@gnu.org; Thu, 02 Jan 2020 06:44:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1imytW-0000J5-Fn for guix-patches@gnu.org; Thu, 02 Jan 2020 06:44:02 -0500 Subject: [bug#38576] [PATCH] gnu: r-irkernel: Fix R kernel loading Resent-Message-ID: From: Ludovic =?UTF-8?Q?Court=C3=A8s?= References: <20191212074613.GA11713@zpidnp36> <87wob13mpn.fsf@elephly.net> <20191212100452.GE22717@zpidnp36> <87r210j5kq.fsf@gnu.org> <20200102073536.GA3066@zpidnp36> Date: Thu, 02 Jan 2020 12:43:51 +0100 In-Reply-To: <20200102073536.GA3066@zpidnp36> (Lars-Dominik Braun's message of "Thu, 2 Jan 2020 08:35:36 +0100") Message-ID: <87h81ew0aw.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Lars-Dominik Braun Cc: Ricardo Wurmus , 38576@debbugs.gnu.org Hi, Lars-Dominik Braun skribis: >> An argument in favor of the status quo would be that it allows users to >> choose between =E2=80=98r=E2=80=99 and =E2=80=98r-minimal=E2=80=99. Is = that a compelling argument? > reading the documentation I thought this was possible using > --with-input=3Dr-minimal=3Dr ? Yes, good point. >> However, if we go that route, we should arrange to not propagate >> =E2=80=98r-minimal=E2=80=99 (it=E2=80=99s intrusive) and instead have = =E2=80=98kernel.json=E2=80=99 do the right >> thing. > I=E2=80=99m not following, sorry. What do you suggest kernel.json should = do? I was suggesting hard-coding the file name of the =E2=80=98R=E2=80=99 execu= table in =E2=80=98kernel.json=E2=80=99, but I see you already did that in your initi= al patch. Sorry for the confusion. On second thought, I think propagating R is acceptable in this case because a Jupyter kernel is a thin wrapper around a programming language implementation. Unless there are objections, I=E2=80=99ll apply your initial patch. Apologies for the delay, but I think it was good to have this discussion! Thanks, Ludo=E2=80=99.