unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Nils Landt <nils@landt.email>
To: Tomas Volf <~@wolfsden.cz>, help-guix@gnu.org
Subject: Re: How to use guix-for-channels together with -L without errors?
Date: Thu, 15 Aug 2024 19:14:52 +0200 (CEST)	[thread overview]
Message-ID: <883867975.432417.1723742092236@office.mailbox.org> (raw)
In-Reply-To: <Zr0ukQPSYqR8LBNZ@ws>

> Tomas Volf <~@wolfsden.cz> hat am 15.08.2024 00:24 CEST geschrieben:
>
> Now, what I do not understand is why this error:
> 
>     no code for module (foo)
> 
> is there.  I am building guix from %default-channels, why is it even loading
> files in the local directory?  And how do I make it stop?  In this case, I could
> just drop `-L .', but in real code I need the argument to load modules required
> for the system.

When that happened to me, it took me forever to find out, so I'm happy to save you some pain:
The -L adds to the *package* module search path. Guix loads all the scm files there to get the package definitions, I'm guessing so there doesn't need to be empty modules with a huge "requires" list of every package-containing module.

So I put my package definitions in a subdirectory of the channels directory, add that subdirectory to GUIX_PACKAGE_PATH, and add the channel root directory to GUILE_LOAD_PATH.


  reply	other threads:[~2024-08-15 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 22:24 How to use guix-for-channels together with -L without errors? Tomas Volf
2024-08-15 17:14 ` Nils Landt [this message]
2024-08-15 19:46   ` Tomas Volf
2024-08-16  4:40     ` Nils Landt

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=883867975.432417.1723742092236@office.mailbox.org \
    --to=nils@landt.email \
    --cc=help-guix@gnu.org \
    --cc=~@wolfsden.cz \
    /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).