From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>, help-guix@gnu.org
Subject: Re: “Guix Profiles in Practice”
Date: Thu, 31 Oct 2019 12:25:01 +0100 [thread overview]
Message-ID: <87k18l5f8y.fsf@ambrevar.xyz> (raw)
In-Reply-To: <22dbbd65-4234-cfcc-970e-feee22e41c4a@crazy-compilers.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Actually maybe we could generalize both features into one.
What's the difference between the two approaches?
- `guix develop' takes a path and guesses the manifest spec filename.
- `guix install-manifest' takes a manifest spec filename as argument.
What about supporting both? It's easy, we simply need to check if the
argument is a folder or not.
David that the manifest be installed to ~/.guix-develop-profile. I
suggest instead that we all manifest have their own folder,
e.g. according to their path.
For example
- foo/bar/manifest.scm -> ~/.guix-extra-profiles/foo/bar
- foo2/bar/manifest.scm -> ~/.guix-extra-profiles/foo2/bar
This way the user needs not worry that the profiles get overwritten.
David suggested that the command automatically activated the profile.
To achieve this would could implement `guix environment --profile
/path/to/profile', and `guix develop` would run this automatically in
the background.
Thoughts?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-10-31 11:25 UTC|newest]
Thread overview: 43+ 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
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-10-27 18:50 ` Hartmut Goebel
2019-10-27 19:06 ` Pierre Neidhardt
2019-10-27 20:56 ` Hartmut Goebel
2019-10-27 21:08 ` Pierre Neidhardt
2019-10-30 14:06 ` Hartmut Goebel
2019-10-31 11:25 ` Pierre Neidhardt [this message]
2019-11-01 13:26 ` Hartmut Goebel
2019-11-01 19:15 ` Pierre Neidhardt
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:00 ` Chris Marusich
2019-10-28 7:59 ` Pierre Neidhardt
2019-10-26 18:32 ` Alex Griffin
2019-10-26 19:38 ` Pierre Neidhardt
2019-10-27 18:54 ` Hartmut Goebel
2019-10-27 19:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k18l5f8y.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=h.goebel@crazy-compilers.com \
--cc=help-guix@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.