unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Reepca Russelstein <anotherreepca@gmail.com>
Cc: 24686@debbugs.gnu.org
Subject: bug#24686: --load-path not honored by guix system
Date: Mon, 17 Oct 2016 10:29:32 +0200	[thread overview]
Message-ID: <87mvi3fker.fsf@gnu.org> (raw)
In-Reply-To: <CA+jmvS7n8sDEtH_LXv9a=openB2zq_Or0GdZjdhj199Y7=9qiA@mail.gmail.com> (Reepca Russelstein's message of "Sun, 16 Oct 2016 20:34:25 -0500")

Reepca Russelstein <anotherreepca@gmail.com> skribis:

> guix --version returns "guix (GNU Guix) 20161013.22". My config.scm
> included (firmware (cons openfwwf-firmware %base-firmware)). I was using a
> patch provided by bavier from irc to provide openfwwf-firmware (here is the
> patch http://paste.lisp.org/display/328373). I created
> /root/guix-modules/gnu/packages/firmware.scm, which was the patched
> version. When I tried running "guix system reconfigure
> --load-path=/root/guix-modules /etc/config.scm" it said that it could not
> find openfwwf-firmware. I then ran "export
> GUIX_PACKAGE_PATH=/root/guix-modules" and then ran "guix system reconfigure
> /etc/config.scm" and it successfully found openfwwf-firmware and
> reconfigured the system. That's why I think --load-path is not being
> honored.

I think there’s something subtle going on.  %load-path is adjusted when
command-line arguments are processed, but that happens after (gnu
system) and presumably (gnu packages firmware) have been loaded.
Therefore, your own (gnu packages firmware) module isn’t “seen”.

What I would suggest is to rename your (gnu packages firmware) module
to, say, (my packages firmware), and to use that in your OS config (make
sure to rename both the file and the module name that appears in the
‘define-module’ clause!).

Could you try and report back?

Thanks,
Ludo’.

      reply	other threads:[~2016-10-17  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13 23:48 bug#24686: --load-path not honored by guix system Blah Blahh
2016-10-16 19:24 ` Ludovic Courtès
2016-10-17  1:34   ` Reepca Russelstein
2016-10-17  8:29     ` Ludovic Courtès [this message]

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=87mvi3fker.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=24686@debbugs.gnu.org \
    --cc=anotherreepca@gmail.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 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).