From: Jonathan Frederickson <jonathan@terracrypt.net>
To: guix-devel@gnu.org
Subject: Re: “Guix Profiles in Practice”
Date: Fri, 25 Oct 2019 20:34:04 -0400 [thread overview]
Message-ID: <84995292-3551-2323-15d9-6ade421d030f@terracrypt.net> (raw)
In-Reply-To: <CAJ=RwfZMBz1aGG24TtCc22sk6Z2PYNGCr8ccCe5+4Y31PQ6v9A@mail.gmail.com>
On 10/25/19 12:36 PM, Thompson, David wrote
> 'guix environment' is a very composable command, and it's not clear to
> me how I would add the stuff I want onto it and it's even less clear
> if it's a good idea. Probably not. So, I wonder if maybe a new
> subcommand, say 'guix develop', could address this common development
> use-case while allowing 'guix environment' to continue being the swiss
> army knife that it is. Some simple naming conventions could make this
> tool "just work." Running 'guix develop' would check for a profile
> symlink with some canonical name, for example '.guix-develop-profile'.
> If it exists, it applies the environment variables and spawns a
> subshell. If it doesn't exist, it looks for a 'develop.scm' file
> (canonical name TBD), builds the profile, symlinks it to
> '.guix-develop-profile', and then does the prior steps. The tool
> would provide a mechanism to update, etc. and it could even be
> expanded later to spawn services like databases.
I love this idea, though I'd like to expand upon that a bit. There's
another tool in the Python world that does something similar called
Pipenv. The gist of it is:
Pipfile: analogous to a Guix manifest
Pipfile.lock: analogous to a Guix manifest + channel spec (this file
contains precisely specified dependency versions)
~/.local/share/virtualenvs/<venv name>: Generated virtualenvs (analogous
to a Guix profile, of course)
You work with these as follows:
$ pipenv install
^ creates a virtualenv with packages from Pipfile.lock (if it exists)
otherwise creates a virtualenv with packages from Pipfile and (by
default) creates Pipfile.lock
$ pipenv lock
^ resolves dependencies for packages in Pipfile and (re)creates Pipfile.lock
$ pipenv shell
^ spawns a subshell in the project's virtualenv
It occurs to me that you could nicely replicate this behavior in Guix by
doing much the same thing; have a convenience command that reads a
manifest with a well-known filename, creates profiles in a well-known
location, and generates a channel spec (probably the current version of
Guix the first time it's run). The end result is that a user could clone
a project with both a manifest and channel spec and end up in the same
environment by just running 'guix develop'.
next prev parent reply other threads:[~2019-10-26 0:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 10:24 “Guix Profiles in Practice” Ludovic Courtès
2019-10-25 16:36 ` Thompson, David
2019-10-25 20:44 ` Pjotr Prins
2019-10-26 10:02 ` Pierre Neidhardt
2019-10-27 8:56 ` Pjotr Prins
2019-10-27 11:30 ` Pierre Neidhardt
2019-10-27 11:43 ` Hartmut Goebel
2019-10-27 20:06 ` Konrad Hinsen
2019-10-27 21:05 ` Pierre Neidhardt
2019-10-28 16:20 ` Konrad Hinsen
2019-10-30 8:36 ` Pierre Neidhardt
2019-10-26 0:34 ` Jonathan Frederickson [this message]
2019-10-26 1:19 ` Jonathan Frederickson
2019-10-26 10:00 ` Pierre Neidhardt
2019-10-27 3:29 ` Bengt Richter
2019-10-27 8:49 ` Pierre Neidhardt
2019-10-27 13:33 ` Konrad Hinsen
2019-10-27 13:53 ` Jelle Licht
2019-11-03 14:24 ` Ludovic Courtès
2019-11-03 16:49 ` Jonathan Frederickson
2019-11-04 10:12 ` Pierre Neidhardt
2019-11-04 14:33 ` Ludovic Courtès
2019-11-04 10:10 ` Pierre Neidhardt
2019-11-05 22:18 ` Carlo Zancanaro
2019-11-06 8:32 ` Pierre Neidhardt
2019-11-06 17:37 ` Ludovic Courtès
2019-11-07 12:42 ` Pierre Neidhardt
2019-10-26 18:32 ` Alex Griffin
2019-10-26 19:38 ` Pierre Neidhardt
-- strict thread matches above, loose matches on Subject: below --
2019-11-02 18:51 Tanguy Le Carrour
2019-11-02 19:21 ` Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84995292-3551-2323-15d9-6ade421d030f@terracrypt.net \
--to=jonathan@terracrypt.net \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).