[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The future of 'guix environment'
From: |
Ludovic Courtès |
Subject: |
Re: The future of 'guix environment' |
Date: |
Thu, 31 Aug 2017 17:00:04 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Hello!
Ricardo Wurmus <address@hidden> skribis:
> @Dave: I pretty much agree with all of the proposed changes. One thing
> that may be lost, though, when using a new <guix-environment> 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 <package> to
<environment>, such that you can still have a guix.scm file that defines
a package and can be passed both to ‘guix package -f’ and ‘guix
environment’.
Ludo’.
- The future of 'guix environment', Thompson, David, 2017/08/30
- Re: The future of 'guix environment', Andreas Enge, 2017/08/30
- Re: The future of 'guix environment', Jan Nieuwenhuizen, 2017/08/31
- Re: The future of 'guix environment', Ludovic Courtès, 2017/08/31
- Re: The future of 'guix environment', Christopher Allan Webber, 2017/08/31