From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Wingo Subject: Re: potluck in the house Date: Tue, 18 Apr 2017 08:49:10 +0200 Message-ID: <878tmy43dl.fsf@igalia.com> References: <87inm8mhzv.fsf@gnu.org> <87h91rduab.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:4830:134:3::10]:33639) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d0MxV-0000xp-Sl for guix-devel@gnu.org; Tue, 18 Apr 2017 02:49:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d0MxS-0000LC-Ph for guix-devel@gnu.org; Tue, 18 Apr 2017 02:49:53 -0400 In-Reply-To: <87h91rduab.fsf@gnu.org> ("Ludovic =?utf-8?Q?Court=C3=A8s=22'?= =?utf-8?Q?s?= message of "Fri, 14 Apr 2017 14:54:04 +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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org On Fri 14 Apr 2017 14:54, ludo@gnu.org (Ludovic Court=C3=A8s) writes: >> I think we should make it so that the lower-potluck-package process >> prefers "core" packages if available, and only goes to the channel if >> the core does not provide a package matching the specification. >> >> I think this is a question for the design of channels though: how to >> resolve dynamically scoped (specification->package) links in the >> presence of channels. > > =E2=80=98specification->package=E2=80=99 already transparently handles th= ings in > GUIX_PACKAGE_PATH, so I suspect it wouldn=E2=80=99t be very different. > > WDYT? I don't know. I see a danger if person A makes a potluck package for that depends on Guile, and person B makes a potluck package for some development version of Guile with a later version number. Person A (and person A's users) probably don't expect to be using a development Guile, so the specifications in person A's package should probably *not* resolve person B's guile as the "best" one. See what I'm saying? Tricky stuff. A hierarchy of potential sources sounds best to me so that specification->package only looks for "guile" in the potluck GUIX_PACKAGE_PATH if it's not found (possibly with the version constraint) in the "main" GUIX_PACKAGE_PATH. Andy