all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ison <ison@airmail.cc>
To: help-guix@gnu.org
Subject: A few questions about channels
Date: Wed, 24 Apr 2019 16:46:55 -0600	[thread overview]
Message-ID: <20190424224654.td7fwnjjf4hnguyc@cf0> (raw)

Several questions about channels have been on my mind which I haven't been able to find any documentation on. So I figured I would ask them all in one place since they seem like fairly standard questions that could help others setting up channels in the future as well.

1) Is it possible to make a channel from a local git repository? (That is to say, a directory on the local machine initialized as a git repository)

2) Is it possible to use private remote repositories as channels? The issue here seems to be one of authentication. I'm wonder if there is (or should be) an "authentication" field one would add to the channel definition in the channels.scm file.

3) How can a channel provide patch files which can be used with "search-patches"? I attempted to look through the guix code in gnu/packages.scm and from what I can tell it looks like search-patches only looks in paths included from "%load-path". There is also a comment saying that it picks up the paths from $GUIX_PACKAGE_PATH, but I thought that variable was being deprecated in favor of channels. If so, shouldn't search-patches also look inside the channels repository for patch files?

             reply	other threads:[~2019-04-24 22:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 22:46 ison [this message]
2019-04-25  8:18 ` A few questions about channels 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190424224654.td7fwnjjf4hnguyc@cf0 \
    --to=ison@airmail.cc \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.