From: Tomas Volf <~@wolfsden.cz>
To: Richard Sent <richard@freakingpenguin.com>
Cc: ludo@gnu.org, help-guix@gnu.org
Subject: Re: Why are custom channels not available to guix repl?
Date: Sat, 13 Jul 2024 16:49:02 +0200 [thread overview]
Message-ID: <ZpKT3suZ_dZ471Rl@ws> (raw)
In-Reply-To: <87plriwvam.fsf@freakingpenguin.com>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
Hello,
On 2024-07-12 10:15:45 -0400, Richard Sent wrote:
> Hi Tomas,
>
> > However when I start `guix repl' and try to use modules from those extra
> > channels, it does not work:
>
> I believe you're being hit with https://issues.guix.gnu.org/61343,
> "modules from channels is not available to "guix repl".
Based on reading the issue that sound like me problem, yes.
>
> As a workaround try ,use (gnu packages). That module has a destructive
> setter (%package-module-path I believe) that extends the load path. That
> should resolve your issue.
>
> Ideally the issue itself would be resolved of course. I believe a
> solution has been identified. There was a comment by Ludo regarding
> program name memoization that's beyond my understanding so I don't know
> what else needs to be done [1].
>
> [1]: https://issues.guix.gnu.org/61343#12
Indeed, importing (gnu packages) does fix it. Thank you very much, I can just
stuff it into .guile for now. Or I guess I could just apply your last patch to
my tree.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-07-13 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 8:11 Why are custom channels not available to guix repl? Tomas Volf
2024-07-12 14:15 ` Richard Sent
2024-07-13 14:49 ` Tomas Volf [this message]
2024-07-13 15:55 ` Suhail Singh
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=ZpKT3suZ_dZ471Rl@ws \
--to=~@wolfsden.cz \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
--cc=richard@freakingpenguin.com \
/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.