From: Jelle Licht <jlicht@fsfe.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>, help-guix@gnu.org
Subject: Re: Guix repl load-path confusion
Date: Sat, 21 Mar 2020 22:40:22 +0100 [thread overview]
Message-ID: <87pnd5bd4p.fsf@jlicht.xyz> (raw)
In-Reply-To: <87pnd5czur.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> No clue but for what it's worth, I can't reproduce on Guix
> ce226e9d8d52d2530f057f2000d36c0d55380ade :p
Tldr: Loading the modules in $HOME/.config/guix/current in a guile repl
breaks building packages when there are overlapping directories between
your configured guix channels.
Thanks! I finally figured it out. This has to do with overlapping
directory trees in guix channels. If you have a channel which has either
an overlapping `gnu/packages/...' (my channel) or for example the guix
home manager channel (with `guix/scripts/...'), you run into these
obscure issues.
As I can simply use my own prefixed directory structure for my own
channel, and AFAICS there has already been gwl related discussions on
how to package guix extensions such as home manager, this issue is
easily prevented.
The reason why I ran into this problem is that that
building/installing/doing anything cool with emacs-guix consistently
triggered this bug for me, as they used a repl in the background with
the appropriate load-path set up.
Should we consider this behavior a bug in guix, or simply a caveat that
we should document in the manual section on channels?
- Jelle, who is extremely psyched about finally finding the cause
of an issue that has been bothering me for 4 years :D
next prev parent reply other threads:[~2020-03-21 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 18:42 Guix repl load-path confusion Jelle Licht
2020-03-21 18:44 ` Pierre Neidhardt
2020-03-21 21:40 ` Jelle Licht [this message]
2020-03-22 7:32 ` 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=87pnd5bd4p.fsf@jlicht.xyz \
--to=jlicht@fsfe.org \
--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.
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).