From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: [PATCH] gnu packages: Add 'specifications->inputs'. Date: Wed, 01 Feb 2017 23:32:37 +0100 Message-ID: <87shnx8rui.fsf@gnu.org> References: <20170129154036.21761-1-mthl@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]:49031) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZ3SJ-00052O-FQ for guix-devel@gnu.org; Wed, 01 Feb 2017 17:32:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZ3SI-0000fy-RC for guix-devel@gnu.org; Wed, 01 Feb 2017 17:32:47 -0500 In-Reply-To: <20170129154036.21761-1-mthl@gnu.org> (Mathieu Lirzin's message of "Sun, 29 Jan 2017 16:40:36 +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: Mathieu Lirzin Cc: guix-devel@gnu.org Mathieu Lirzin skribis: > * gnu/packages.scm (specifications->inputs): New procedure. > --- > > Hi, > > Using 'specification->package' is not convenient for package inputs in > 'guix.scm' development packages because it involves either using it over = and > over or defining a custom procedure. I think it would be nice if Guix was > providing a concise way to achieve the desired result. > > This patch is an attempt to fix that inconvenience. Thanks. Makes sense. What about adding an example for --load under =E2=80=9CInvoking guix environment=E2=80=9D? For instance just showing how the example already th= ere is written when using =E2=80=98specifications->inputs=E2=80=99 instead of e= xplicit variable reference. OK with something along these lines! Thanks, Ludo=E2=80=99.