From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: 02/02: gnu: next: Compress the executable. Date: Mon, 16 Sep 2019 17:56:02 +0200 Message-ID: <8736gw6xrh.fsf@gnu.org> References: <20190905095602.15524.75425@vcs0.savannah.gnu.org> <20190905095603.AC57A209A5@vcs0.savannah.gnu.org> <874l1qgc1j.fsf@elephly.net> <871rwuc3es.fsf@ambrevar.xyz> <87blvu32qm.fsf@gnu.org> <878sqxq4ga.fsf@ambrevar.xyz> <875zm0co0t.fsf@ambrevar.xyz> <87h85ipo14.fsf@gnu.org> <87muf9n8sc.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:36542) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i9tMD-0007Vd-81 for guix-devel@gnu.org; Mon, 16 Sep 2019 11:56:06 -0400 In-Reply-To: <87muf9n8sc.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Thu, 12 Sep 2019 11:49:55 +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: Pierre Neidhardt Cc: guix-devel@gnu.org Pierre Neidhardt skribis: > And... I have so many more questions! > >> =E2=80=98guix size=E2=80=99 and =E2=80=98guix gc -R=E2=80=99 show you th= e whole closure of the store >> item, so you might not realize that some of the things that ought to be >> direct dependencies are now in fact indirect dependencies. >> >> If sqlite ought to be a direct dependency and is now, in fact, an >> indirect dependency, things won=E2=80=99t break right away: sqlite won= =E2=80=99t be >> deleted as long as next is live. >> >> But you=E2=80=99ll already run into problems: grafting will yield a brok= en next, >> as in . > > I think the aforementioned issue is different: it's about store paths > that are written within Common Lisp code, which only happens here for > the next-gtk-webkit executable. This is not related to SQLite or > others, which are visible to the reference scanner. > > I don't understand how grafting could cause a problem: next-1.3.1-lib > would still be present, right? Same story: if the reference to =E2=80=98next-1.3.1-lib=E2=80=99 is invisib= le to the scanner or grafting code (due to compression, or due use of a non-ASCII compatible string encoding), the =E2=80=98next-1.3.1-lib=E2=80=99 might van= ish. Ludo=E2=80=99.