From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: shepherd -> guile 2.2? Date: Wed, 17 May 2017 15:02:28 +0200 Message-ID: <87fug3y6u3.fsf@gnu.org> References: <878tlx5h10.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50142) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dAyb4-0001oB-V5 for guix-devel@gnu.org; Wed, 17 May 2017 09:02:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dAyb1-0000pn-RO for guix-devel@gnu.org; Wed, 17 May 2017 09:02:35 -0400 In-Reply-To: <878tlx5h10.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 16 May 2017 10:42:51 +0200") 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.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel@gnu.org Hi Ricardo, Ricardo Wurmus skribis: > I have built shepherd with guile-2.2, but I noticed a couple of > warnings/errors during the build: I=E2=80=99m pretty sure those warnings are due to =C2=A0IOFBF and friends. = They=E2=80=99ll haunt us for years to come. :-) (But you can happily ignore them.) > And lastly: should we keep a guile-2.0 variant of the shepherd, or is it > fine to push this tiny change? No, we can do that in =E2=80=98core-updates=E2=80=99 only. The reason is that we import code in the Shepherd, via the gexps in the =E2=80=98start=E2=80=99 and =E2=80=98stop=E2=80=99 fields of , and those modules are currently built with =E2=80=98default-guile=E2=80=99, which is 2.0 in maste= r and 2.2 in =E2=80=98core-updates=E2=80=99. So yeah, in =E2=80=98core-updates=E2=80=99, we can happily move the Shepher= d and mcron to 2.2, but not in =E2=80=98master=E2=80=99. Ludo=E2=80=99.