From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:56782) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hNZEB-0002iZ-5u for guix-patches@gnu.org; Mon, 06 May 2019 04:44:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hNZEA-0004KO-5d for guix-patches@gnu.org; Mon, 06 May 2019 04:44:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:42129) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hNZEA-0004KH-2H for guix-patches@gnu.org; Mon, 06 May 2019 04:44:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hNZE9-0005D6-UA for guix-patches@gnu.org; Mon, 06 May 2019 04:44:01 -0400 Subject: [bug#35388] [PATCH] gnu: julia: Update to 1.1.0 Resent-Message-ID: From: Ludovic =?UTF-8?Q?Court=C3=A8s?= References: <0190423085235.21419-1-anothersms@gmail.com> <20190425075114.10284-1-anothersms@gmail.com> Date: Mon, 06 May 2019 10:43:11 +0200 In-Reply-To: <20190425075114.10284-1-anothersms@gmail.com> ("=?UTF-8?Q?Nicol=C3=B2?= Balzarotti"'s message of "Thu, 25 Apr 2019 09:51:14 +0200") Message-ID: <87ftpsm0rk.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: =?UTF-8?Q?Nicol=C3=B2?= Balzarotti Cc: 35388@debbugs.gnu.org Hi Nicol=C3=B2, Nicol=C3=B2 Balzarotti skribis: > One second problem regards the llvm patches. They should be generic (as s= tated > in the link in the patch, [2]) but are actually needed to compile julia (= so I > cannot use pure system llvm, but I don't feel like applying them to system > llvm all by myself). OK. > The .patch files are available in the julia source package: is it ok to p= lace them in the patches folder or shuld I fetch the julia source and extra= ct them during build? It would be best if they could be downloaded from upstream. For that you could use one =E2=80=98origin=E2=80=99 for each patch and use them dire= ctly in the =E2=80=98patches=E2=80=99 field. Alternately, if that=E2=80=99s more conve= nient, you could add one =E2=80=98origin=E2=80=99 for the whole repository, and add an =E2=80=98= apply-patches=E2=80=99 to the =E2=80=98llvm-julia=E2=80=99 package that would pick patches in the right p= lace. Could you also try to provide a commit log listing all the changes that this patch makes? You can read =E2=80=98git log=E2=80=99 for examples or s= ee . Other than that I think it should be ready to go, and I=E2=80=99m really ha= ppy a newer Julia package is around the corner! Thank you, and apologies for the delay! Ludo=E2=80=99.