From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>, help-guix@gnu.org
Subject: Re: “Guix Profiles in Practice”
Date: Sun, 27 Oct 2019 21:56:59 +0100 [thread overview]
Message-ID: <8cad953f-09a1-97b9-7c61-62161bd1e0a3@crazy-compilers.com> (raw)
In-Reply-To: <878sp66mas.fsf@ambrevar.xyz>
Am 27.10.19 um 20:06 schrieb Pierre Neidhardt:
> I think it's useful to support multiple directories since it's likely
> that users will work on multiple projects.
>
> See what I've done for Emacs-Guix. The (configurable) file structure
> looks like this:
>
> - ~/.guix-extra-profiles/my-project
> - ~/.guix-extra-manifests/my-project
> - ~/.guix-extra-channels/my-project
AFAIU David (and this is what I meant, too), is to have the
"develop.scm" (or ".guix-develop-profile.scm") in the project working
tree. This would allow to easily maintain the profile together with the
source and a simple workflow like
cd /path/to/my-project
guix develop
or
guix develop /path/to/my-project
> Then I can do "guix-install-manifest", Emacs prompts me for a manifest
> name in ~/.guix-extra-manifests (with completion), and does all the
> necessary to install it in ~/.guix-extra-profiles. It dumps the channel
> specification in ~/.guix-extra-channels/my-project.
IMHO this is a too emacs-centric approach. We should also have in mind
those not using guix-mode and not even using emacs.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2019-10-27 20:57 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 [this message]
2019-10-27 21:08 ` Pierre Neidhardt
2019-10-30 14:06 ` Hartmut Goebel
2019-10-31 11:25 ` Pierre Neidhardt
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=8cad953f-09a1-97b9-7c61-62161bd1e0a3@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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.