From debbugs-submit-bounces@debbugs.gnu.org Thu Jan 02 06:44:01 2020 Received: (at 38576) by debbugs.gnu.org; 2 Jan 2020 11:44:01 +0000 Received: from localhost ([127.0.0.1]:38330 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1imytU-0000Ii-Vf for submit@debbugs.gnu.org; Thu, 02 Jan 2020 06:44:01 -0500 Received: from eggs.gnu.org ([209.51.188.92]:37028) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1imytT-0000IV-Cg for 38576@debbugs.gnu.org; Thu, 02 Jan 2020 06:43:59 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]:54431) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1imytO-0000s8-4A; Thu, 02 Jan 2020 06:43:54 -0500 Received: from [2a01:e0a:1d:7270:af76:b9b:ca24:c465] (port=49598 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1imytN-0005vt-MR; Thu, 02 Jan 2020 06:43:53 -0500 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= To: Lars-Dominik Braun Subject: Re: [bug#38576] [PATCH] gnu: r-irkernel: Fix R kernel loading References: <20191212074613.GA11713@zpidnp36> <87wob13mpn.fsf@elephly.net> <20191212100452.GE22717@zpidnp36> <87r210j5kq.fsf@gnu.org> <20200102073536.GA3066@zpidnp36> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 13 =?utf-8?Q?Niv=C3=B4se?= an 228 de la =?utf-8?Q?R?= =?utf-8?Q?=C3=A9volution?= X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-pc-linux-gnu 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> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 38576 Cc: Ricardo Wurmus , 38576@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) 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.