From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Prevent native-inputs references ending up in the final binary Date: Wed, 24 Jan 2018 15:26:27 +0100 Message-ID: <871sif1gfg.fsf@gnu.org> References: <81597a04-598a-e894-84af-759c1b5401ca@tobias.gr> <20180120001317.GD18016@jasmine.lan> <20180120114059.34736dda@scratchpost.org> <0bde4e06-f0ab-6a6d-2c70-fdd0693b3c3f@tobias.gr> <20180121223714.GA9310@jasmine.lan> <883b5637-01f7-7db3-6a07-956174a65316@tobias.gr> 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]:51851) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eeM0a-0001x5-23 for guix-devel@gnu.org; Wed, 24 Jan 2018 09:26:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eeM0V-0008ND-Ap for guix-devel@gnu.org; Wed, 24 Jan 2018 09:26:36 -0500 Received: from hera.aquilenet.fr ([185.233.100.1]:36838) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eeM0V-0008MU-4x for guix-devel@gnu.org; Wed, 24 Jan 2018 09:26:31 -0500 In-Reply-To: <883b5637-01f7-7db3-6a07-956174a65316@tobias.gr> (Tobias Geerinckx-Rice's message of "Sun, 21 Jan 2018 23:47:42 +0100") 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: Tobias Geerinckx-Rice Cc: guix-devel@gnu.org Hi, Tobias Geerinckx-Rice skribis: > Leo Famulari wrote on 21/01/18 at 23:37: >> On Sat, Jan 20, 2018 at 04:47:14PM +0100, Tobias Geerinckx-Rice wrote: >>> Danny, >>> >>> Danny Milosavljevic wrote on 20/01/18 at 11:40: >>>> We should change that in core-updates-next, if possible. >>>>=20=20 >>>> I think that native-inputs shouldn't end up in the final binary as a >>>> reference [...] >>> This has been discussed before, and I agree. (I started a branch to do >>> so but it breaks quite a few things and it got tedious. I think I'm >>> ready for more now.) > > [...] > >> I'd rather we do it somewhere else than core-updates. >>=20 >> It's already very difficult to complete the core-updates cycles. We >> should limit core-updates to updates of core packages, and handle big >> changes to Guix itself on their own branches. > > Er, yeah. Definitely. +1 Anyway, I think it=E2=80=99s worth experimenting this on a branch. We=E2= =80=99ll have to expect lots of breakage as Leo writes, so we=E2=80=99ll need to refine t= hings progressively. Once such a branch exist, we can get it built on berlin or hydra. Ludo=E2=80=99.