From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: GUIX_EXTENSIONS_PATH error?
Date: Fri, 15 Jan 2021 23:24:48 +0100 [thread overview]
Message-ID: <87wnwdbzyn.fsf@elephly.net> (raw)
In-Reply-To: <86eeilly1y.fsf@gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
>>> --8<---------------cut here---------------start------------->8---
>>> $ cat /tmp/foo/bar.scm
>>> (define-module (guix extensions bar)
>>> #:use-module (guix scripts))
>>
>> This right here is the problem. The module name and the file name do
>> not match. The file must be
>> $GUIX_EXTENSIONS_PATH/guix/extensions/bar.scm and provide the module
>> (guix extensions bar).
>
> Ah yeah, that makes sense. Now, no error but nothing showed:
>
> --8<---------------cut here---------------start------------->8---
> $ cat $GUIX_EXTENSIONS_PATH/guix/extensions/bar.scm
> (define-module (guix extensions bar)
> #:use-module (guix scripts)
> #:export (guix-bar)
> )
>
>
> (define-command (guix-bar . args)
> (category extension)
> (synopsis "a bar with beer")
>
> (pk "dumb"))
>
> $ guix --help | grep bar
> --8<---------------cut here---------------end--------------->8---
Oh, my bad: $GUIX_EXTENSIONS_PATH must actually include the
“/guix/extensions” sub-directory.
So if the file is at /tmp/foo/guix/extensions/bar.scm then
$GUIX_EXTENSIONS_PATH should be /tmp/foo/guix/extensions.
Sorry for the confusion!
--
Ricardo
next prev parent reply other threads:[~2021-01-15 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 20:33 GUIX_EXTENSIONS_PATH error? zimoun
2021-01-15 20:45 ` Ricardo Wurmus
2021-01-15 20:55 ` zimoun
2021-01-15 22:24 ` Ricardo Wurmus [this message]
2021-01-15 22:32 ` zimoun
2021-01-15 22:42 ` Ricardo Wurmus
2021-01-15 22:58 ` zimoun
2021-01-15 23:17 ` Ricardo Wurmus
2021-01-16 1:49 ` zimoun
2021-02-01 7:41 ` GUIX_EXTENSIONS_PATH pattern zimoun
2021-02-08 22:37 ` Ricardo Wurmus
2021-02-09 0:40 ` zimoun
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=87wnwdbzyn.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@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).