From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: The future of 'guix environment' Date: Thu, 31 Aug 2017 17:00:04 +0200 Message-ID: <87efrrok97.fsf@gnu.org> References: <87ziahytsq.fsf@member.fsf.org> <87lgm1f4ci.fsf@elephly.net> 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]:55901) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dnQx2-000748-AZ for guix-devel@gnu.org; Thu, 31 Aug 2017 11:00:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dnQww-0004zX-Nz for guix-devel@gnu.org; Thu, 31 Aug 2017 11:00:12 -0400 In-Reply-To: <87lgm1f4ci.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 30 Aug 2017 17:43:57 +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: Ricardo Wurmus Cc: guix-devel Hello! Ricardo Wurmus skribis: > @Dave: I pretty much agree with all of the proposed changes. One thing > that may be lost, though, when using a new record is > easy ad-hoc packaging. > > Now I can use a guix.scm file both for building a Guix package and a > Docker image; I would expect that it would no longer be possible to > build a Guix package out of an environment file. On the other hand, > building a more fully featured container image would be even simpler > with this change. I think the new command could automatically convert to , such that you can still have a guix.scm file that defines a package and can be passed both to =E2=80=98guix package -f=E2=80=99 and = =E2=80=98guix environment=E2=80=99. Ludo=E2=80=99.