From mboxrd@z Thu Jan 1 00:00:00 1970 From: Efraim Flashner Subject: Re: Guile 3 migration plan Date: Thu, 16 Jan 2020 16:57:31 +0200 Message-ID: <20200116145731.GB23583@E5400> References: <874kwvemsw.fsf@inria.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="PmA2V3Z32TCmWXqI" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57323) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1is6bW-0007Ka-Dd for guix-devel@gnu.org; Thu, 16 Jan 2020 09:58:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1is6bS-0008Fg-Pe for guix-devel@gnu.org; Thu, 16 Jan 2020 09:58:38 -0500 Content-Disposition: inline In-Reply-To: <874kwvemsw.fsf@inria.fr> 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-mx.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Guix-devel --PmA2V3Z32TCmWXqI Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 16, 2020 at 11:08:15AM +0100, Ludovic Court=C3=A8s wrote: > Hello Guix! >=20 > Today is Guile 3 day, a day to celebrate, woohoo! \o/ >=20 > How will Guix migrate to Guile 3? That=E2=80=99s a threefold process: >=20 > 1. We must first migrate packages. I propose to rename =E2=80=9Cguile-= next=E2=80=9D > to =E2=80=9Cguile=E2=80=9D today, such that =E2=80=9Cguix install gu= ile=E2=80=9D will now install > Guile 3 (no mass rebuild involved: the =E2=80=9Cdefault=E2=80=9D Gui= le remains > 2.2.) >=20 > The downside is that if you run =E2=80=9Cguix install guile guile-js= on=E2=80=9D, > you=E2=80=99ll get Guile 3 with Guile-JSON for 2.2; instead, you hav= e to > explicitly select =E2=80=9Cguile3.0-json=E2=80=9D. I feel like these should move together. Imagine if we had python libraries that only worked with python2 but called them python-foo anyway. Having consistent naming between the packages is important. >=20 > I propose renaming all the =E2=80=9Cguile3.0-=E2=80=9D packages to = =E2=80=9Cguile-=E2=80=9D, and > all the =E2=80=9Cguile-=E2=80=9D packages to =E2=80=9Cguile2.2-=E2= =80=9D as a second step, which > will address this issue. This could be done within a few days or > weeks. It seems to me we could switch the guile packages to guile3.0 and leave guix at guile2.2. In any case, we should create a guix-with-guile3 package to encourage people to try to fix bugs and try it out. >=20 > 2. We must be able to run Guix itself on Guile 3. This is already > possible if you add =E2=80=9C3.0=E2=80=9D to the =E2=80=98GUILE_PKG= =E2=80=99 invocation in > =E2=80=98configure.ac=E2=80=99, but there are still a few test failu= res that I=E2=80=99ve > been working on. Almost all of them relate to the use of =E2=80=98@= @=E2=80=99 and > =E2=80=98mock=E2=80=99, which do not work with Guile 3 =E2=80=9Cdecl= arative modules=E2=80=9D. >=20 > In many cases, it=E2=80=99s an opportunity to clean up our tests; se= e for > example 4aea90b1876179aab8d603a42533a6bdf97ccd3c and the preceding > commit. It should be possible to be done real soon! I'm going to miss '@@' >=20 > Once we=E2=80=99re done, we can change (guix self) so that =E2=80=98= guix pull=E2=80=99 > pulls Guix on Guile 3. >=20 > 3. Change =E2=80=98default-guile=E2=80=99 to point to Guile 3 in =E2=80= =98core-updates=E2=80=99, and > switch all the packages that consume .go files coming from > =E2=80=98with-imported-modules=E2=80=99 to Guile 3, in particular = =E2=80=98shepherd=E2=80=99 and > =E2=80=98mcron=E2=80=99. >=20 > Thoughts? >=20 > You can celebrate Guile 3 day by helping out any of these! Let=E2=80=99s > synchronize here and on IRC! :-) >=20 > Ludo.=E2=80=99 >=20 --=20 Efraim Flashner =D7=90=D7=A4=D7=A8=D7=99=D7=9D = =D7=A4=D7=9C=D7=A9=D7=A0=D7=A8 GPG key =3D A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted --PmA2V3Z32TCmWXqI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAl4gedcACgkQQarn3Mo9 g1GQtw//QsevbSoYGjmFnY4S756Mbsmd8GU+7gcn1cRMOaQ8pNgXGTOMAJYLTp9l VWYfbp7x/OWP++6eOi9sV9TcRPmCKqqPGng8SldqjCu96+qSX6srwDa+PpfcvtAF AVFixNi6t9OFnsa7AjPKNpU4wtSQmiEN3o1xOHoE4xFT33jqBgBzI5zebP/j9kL5 nHwSTKvxJ0X0CkRAkgOEEG+DIXdzKoyNtv2kH3mvXHSkl/492wEMfeUF+JkYiSI4 yi23Y02NNJjlhij+yBb91keAbDko1RaEt3o7xCxs0/+g6b6s96yxwGgT/N6zvftp Tr5g/J5d91RV+3UjNEuxTBSuVBwYUiO+sZYMNU/skICpd8hrZ26taeSrV6nBqWQT EFzcsV8ek9MaSwtKylna2t+jFRbcUBN6CD5zr8SNlq6cc97SxEj9PORq7gBx2xY3 RsrJx1Yln6pYuqTeHptIZIAfLaJpBwUFTMfcHa99MLrYJY37zPE7Q9zAzspi89LD x3XJdy8dYpGK7yUhp409mZFc9PdCWEcY2lW80xhCAg0VF+IfB6mvLuq7W/ud8pjg /12aT01DPtifK4AD0jhGkL0gTmpQ3iG3uq+8XNYMxc8qaCC6VL8eHcXNv58reAap tvm6DbOmMbUbJipMe2K1a9gAaxGUH8F4BEYfFPYVaaLZW7f1KnI= =YMXp -----END PGP SIGNATURE----- --PmA2V3Z32TCmWXqI--