From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: Re: Package inputs in manifests Date: Mon, 18 Nov 2019 17:18:19 +0100 Message-ID: References: <87mudrxvs8.fsf@ambrevar.xyz> <87mudd59ho.fsf@gnu.org> <877e4glyc3.fsf@ambrevar.xyz> <87ftj1x8fw.fsf@gnu.org> <87mucupz8k.fsf_-_@gnu.org> 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]:46196) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iWjjb-0002ml-QN for guix-devel@gnu.org; Mon, 18 Nov 2019 11:18:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iWjja-0006To-KC for guix-devel@gnu.org; Mon, 18 Nov 2019 11:18:39 -0500 In-Reply-To: <87mucupz8k.fsf_-_@gnu.org> 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: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: Guix Devel Hi, On Sun, 17 Nov 2019 at 11:35, Ludovic Court=C3=A8s wrote: > You=E2=80=99re doing it right! It turns out that two different variants = of > =E2=80=9Cgzip=E2=80=9D appear: one in =E2=80=98%final-inputs=E2=80=99 (th= e implicit inputs of > =E2=80=98gnu-build-system=E2=80=99) and another one somewhere else, hence= the collision. > > The solution is to pass =E2=80=98--allow-collisions=E2=80=99, which is wh= at =E2=80=98guix > environment=E2=80=99 does by default precisely for that reason (see commi= t > afd06f605bf88a796acefc7ed598b43879346a6b). Nice! I would be able to find myself! ;-) However, in the commit afd06f605bf88a796acefc7ed598b43879346a6b, the behaviour appears to me inconsistent. On one hand, the default is #f in guix/profiles.scm or in guix/scripts/package.scm, on the other hand the default is #t in guix/scripts/environment.scm. Does a rationale exist for that? Why not turn on #t all the defaults and instead have the option "--no-allow-collisions". Keeping the option "--allow-collisions" for compatibility. > We could check exactly why we end up with several =E2=80=98gzip=E2=80=99 = instances, but > overall I think this kind of thing is hard to avoid for package inputs. Yes, we could investigate from where comes this collisions. Thank you for the explanations and the pointers. All the best, simon