From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: guix-devel@gnu.org
Subject: Re: “Guix Profiles in Practice”
Date: Sat, 02 Nov 2019 20:21:11 +0100 [thread overview]
Message-ID: <87o8xuf5js.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20191102185150.sq2rvjobx5rzww7b@melmoth>
[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]
Hi Tanguy,
Glad you like it!
Tanguy Le Carrour <tanguy@bioneland.org> writes:
> I have two rather simple questions:
> #1. why put the profile in `"$GUIX_EXTRA_PROFILES"/my-project/my-project`
> instead of `"$GUIX_EXTRA_PROFILES"/my-project`? I tried to create 2
> profiles right under `"$GUIX_EXTRA_PROFILES"`, and it seems to work!
Maybe this wasn't completely clear in the article. The reason is that
successive generations create symlinks next to "my-project. In the end,
the file hierarchy will look like this:
$GUIX_EXTRA_PROFILES/my-project/my-project
$GUIX_EXTRA_PROFILES/my-project/my-project-1
$GUIX_EXTRA_PROFILES/my-project/my-project-2
$GUIX_EXTRA_PROFILES/my-project/my-project-3
...
If you have multiple profiles, having a subdir for
each profile makes your life easier.
> #2. how can I remove a profile?! … actually, I figured out that removing
> the links works. Garbage would be (magically) collected on the next
> `guix gc` ("removing stale link from…").
Indeed! ;)
> Is point #2 the reason why the profiles are stored in subfolders?! If
> yes, I would use `"$GUIX_EXTRA_PROFILES"/my-project/current` instead.
> Does it make sense?!
You can use current, the name is arbitrary.
> My actual concern with profiles comes from the fact that I'm a Fish [1]
> user.
This is a known problem and it's being discussed here:
https://lists.gnu.org/archive/html/guix-devel/2019-10/msg00565.html
Your insights are welcome! ;)
> This brings me to my last (but not quite related) question… where does
> `--search-paths` get its information from? I guess it's something in the
> package definition that tells it "you have to export PYTHONPATH", but
> I'm not sure where. Any clue welcome!
Look at the `native-search-path` field in the package definitions.
> Anyway, thanks again for your work on the article!
You're welcome!
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-11-02 19:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 18:51 “Guix Profiles in Practice” Tanguy Le Carrour
2019-11-02 19:21 ` Pierre Neidhardt [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-25 10:24 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-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
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=87o8xuf5js.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=tanguy@bioneland.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).