unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ison <ison@airmail.cc>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: A few questions about channels
Date: Mon, 6 May 2019 15:13:30 -0600	[thread overview]
Message-ID: <20190506211330.o4k4de6il2byu4lb@cf0> (raw)
In-Reply-To: <87woj4xo72.fsf@gmail.com>

> 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.

So for example, if I create a repository with directory structure:
* gnu/packages for .scm package files
* gnu/packages/patches for .patch files
then the packages are correctly added and I can install them like any other
package. But if I add a .patch file into the patches directory and reference it
with (search-patches "filename.patch") it can't find it.

I have also tried various other combinations of the patches directory, including
placing patches in with the package files, placing everything at the root of the
repo, etc.
Perhaps I still just haven't found the right directory structure?

Also in case it matters, I think the patch format is correct as well, because it
succeeds if I don't use search-patches and instead just supply the full path to
the patch file.

> Actually, you can also just write "/home/myuser/src/my-guix-packages".
> The "file://" part is fine to add, but it is not necessary.  I think
> (but am not sure) that you can use any protocol understood by Git here.

Oh, I feel silly for not having tried this. Thanks.

As for the authentication issue, as long as I can do a local repository that's
all I need personally. So I have no strong opinions on how best to handle it.

Thanks for the replies

  reply	other threads:[~2019-05-06 21:13 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 [this message]
2019-05-06 21:43     ` Ricardo Wurmus
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=20190506211330.o4k4de6il2byu4lb@cf0 \
    --to=ison@airmail.cc \
    --cc=cmmarusich@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).