From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, Anthony Quizon <anthoq88@gmail.com>
Subject: Re: installing and searching from custom channel
Date: Wed, 22 Apr 2020 09:29:40 -0400 [thread overview]
Message-ID: <0D03A94B-6DC2-4B36-A709-BD6A0AEC354A@lepiller.eu> (raw)
In-Reply-To: <CAPHgq++AsJpv+kN3Z8LCFdoM8=GX-y3+c53tX+uXFCuvFVReTw@mail.gmail.com>
Le 22 avril 2020 02:23:56 GMT-04:00, Anthony Quizon <anthoq88@gmail.com> a écrit :
>I'm trying to experiment with my own channel packages.
>
>Here is my current channel code:
>https://github.com/anthonyquizon/guix-channel
>
>The docs in https://guix.gnu.org/manual/en/html_node/Channels.html
>mentions
>that if I have packages in a subdirectory, I need to specify its
>location
>in .guix-channel.
>
>However, doing this, 'guix pull' does not work and giving me an error:
>
>
>*|builder for
>`/gnu/store/04xj2y92320w5jd2rs3kqcdd4wxg0w78-anthonyquizon-packages.drv'
>failed to produce output path
>`/gnu/store/ky6097zcynxvwdkmgk5vw7p2qrqwyby8-anthonyquizon-packages'
>
> build of
>/gnu/store/04xj2y92320w5jd2rs3kqcdd4wxg0w78-anthonyquizon-packages.drv
>failed *
>
>(I've renamed .guix-channel to _guix-channel for now)
>
>I tried to add a package in the root folder and was not able to search
>or
>install it via "guix search hello-foo" and "guix install hello-foo"
>after a
>"guix pull".
>
>The package builds fine with "guix build -L . anthony-hello".
>
>Is there something I'm missing?
In your case you don't need a .guix-channel because your package modules are named correctly:
In a/b/c.scm is module (a b c), no need for a .guix-channel
If in a/b/c.scm is module (b c), you'll need to specify a as thc subdirectory where modules are located. Does it make sense?
next prev parent reply other threads:[~2020-04-22 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 6:23 installing and searching from custom channel Anthony Quizon
2020-04-22 13:29 ` Julien Lepiller [this message]
2020-04-23 1:11 ` Anthony Quizon
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=0D03A94B-6DC2-4B36-A709-BD6A0AEC354A@lepiller.eu \
--to=julien@lepiller.eu \
--cc=anthoq88@gmail.com \
--cc=help-guix@gnu.org \
/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).