From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thompson, David" Subject: Re: The future of 'guix environment' Date: Fri, 1 Sep 2017 09:15:50 -0400 Message-ID: References: <87ziahytsq.fsf@member.fsf.org> <20170830155634.GB2248@jurong> <87lglz2hrn.fsf@dustycloud.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60502) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dnlnl-0002FZ-Cu for guix-devel@gnu.org; Fri, 01 Sep 2017 09:16:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dnlng-0006tc-Gy for guix-devel@gnu.org; Fri, 01 Sep 2017 09:16:01 -0400 Received: from mail-ua0-x230.google.com ([2607:f8b0:400c:c08::230]:34418) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dnlng-0006t8-Cp for guix-devel@gnu.org; Fri, 01 Sep 2017 09:15:56 -0400 Received: by mail-ua0-x230.google.com with SMTP id l11so555866uaf.1 for ; Fri, 01 Sep 2017 06:15:56 -0700 (PDT) In-Reply-To: <87lglz2hrn.fsf@dustycloud.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: Christopher Allan Webber Cc: guix-devel On Thu, Aug 31, 2017 at 11:57 PM, Christopher Allan Webber wrote: > Thompson, David writes: > >> Ricardo, you are correct that we would lose the ability to use the >> guix.scm file for both 'guix environment' and 'guix build'. In >> practice I don't actually use my guix.scm file this way, so I think >> it's worth breaking, but maybe you (or someone else) actually uses >> this and we should think more about it? > > I do use guix.scm for testing `guix build'. Maybe I ma the only one > though. It turns out to be very useful to find out whether or not I've > done something that borked my package that's not obvious because I have > some compiled .go file around in working directory or something. Ludovic's suggestion of supporting both package and environment objects with --load will solve the issue. >> I wasn't very clear about whether ephemeral or cached would be the new >> default. I don't think there is one default for all cases, I think >> it's more context sensitive. > > I'm a bit confused by caching, but IMO maybe the right solution is > actually guix environment for "environment profiles". Ie, I want to be > able to update my guix environment and if it turns out I made a mistake > easily roll back, just like I can with my user's profile. Currently > you can use --root, but you don't have the generations support. This is what caching would allow. - Dave