From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:34675) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j2Y5m-0003iW-M5 for guix-patches@gnu.org; Fri, 14 Feb 2020 05:21:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j2Y5l-0004pJ-PZ for guix-patches@gnu.org; Fri, 14 Feb 2020 05:21:02 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:54923) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j2Y5l-0004p4-Mn for guix-patches@gnu.org; Fri, 14 Feb 2020 05:21:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1j2Y5l-0001GD-Jl for guix-patches@gnu.org; Fri, 14 Feb 2020 05:21:01 -0500 Subject: [bug#39547] [PATCH] website: Provide JSON sources list used by Software Heritage. Resent-Message-ID: From: Ludovic =?UTF-8?Q?Court=C3=A8s?= References: <20200210170418.32076-1-zimon.toutoune@gmail.com> <87pnehk1de.fsf@gnu.org> Date: Fri, 14 Feb 2020 11:20:38 +0100 In-Reply-To: (zimoun's message of "Fri, 14 Feb 2020 10:04:01 +0100") Message-ID: <8736bdjwqx.fsf@inria.fr> 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: zimoun Cc: 39547@debbugs.gnu.org Hi, zimoun skribis: >> Could you, in a first patch, move =E2=80=98origin->json=E2=80=99 out of >> =E2=80=98packages-json-builder=E2=80=99, and in a second patch, add mirr= or-expansion >> feature? > > Yes, I will try but I am a bit lost. There is: > - packages-json-builder that I did not modified > - sources-json-builder which the "adaptation" of the former to output > to the sources.json format. > > Well, do you want a refactor of 'origin->json' shared by the 2 > "{sources,packages}-json-builder"? Yes, exactly. No reason to have two copies of that code. > Working on updating the package Julia, I have seen that some patches > are 'origin' and live for example upstream > (https://blablab/project.git/patches/fancy-name.patch) and the current > patch will not list them. Therefore, if upstream disappears and/or > change in-place the patches, Guix would not be able to re-build in the > future (time-machine). Right. I guess you can implement that in the next version. What you propose is already nice to have. Ludo=E2=80=99.