From: Ricardo Wurmus <rekado@elephly.net>
To: ison <ison@airmail.cc>
Cc: help-guix@gnu.org
Subject: Re: A few questions about channels
Date: Mon, 06 May 2019 23:43:20 +0200 [thread overview]
Message-ID: <8736lrfedj.fsf@elephly.net> (raw)
In-Reply-To: <20190506211330.o4k4de6il2byu4lb@cf0>
ison <ison@airmail.cc> writes:
>> This should work just like it would for GUIX_PACKAGE_PATH. Are you
>> saying that the patch files you have created in your channel are not
>> being found?
>
> Correct, they're not being found. But I do not have the variable
> $GUIX_PACKAGE_PATH set, because I thought it was being deprecated. Do I need it
> to make patches work? Everything else seems to work without it except patches.
Here’s a channel I’ve been maintaining long before channels were a
thing: https://github.com/BIMSBbioinfo/guix-bimsb
It includes patch files in the root directory and they are found just
fine.
--
Ricardo
next prev parent reply other threads:[~2019-05-06 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 22:46 A few questions about channels ison
2019-04-25 8:18 ` david.larsson
2019-04-30 19:41 ` Oleg Pykhalov
2019-05-06 3:21 ` Chris Marusich
2019-05-06 21:13 ` ison
2019-05-06 21:43 ` Ricardo Wurmus [this message]
2019-05-07 0:45 ` ison
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=8736lrfedj.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=ison@airmail.cc \
/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).