all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: david.larsson@selfhosted.xyz
Cc: help-guix@gnu.org
Subject: Re: A few questions about channels
Date: Tue, 30 Apr 2019 22:41:59 +0300	[thread overview]
Message-ID: <875zqv5lh4.fsf@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.21.9999.1904251017290.13609@localhost> (david larsson's message of "Thu, 25 Apr 2019 10:18:07 +0200 (CEST)")

[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]


[…]

>> 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.
>>
> I agree it would be nice to have. The git-fetch method is defined
> here:
> https://github.com/guix-mirror/guix/blob/012bf5c4c03e30633f137960bd0677e204c638a7/guix/build/git.scm
> and I think it can be modified without too much effort to include an
> argument for the -key flag to the git command. I am not sure though
> whether git-fetch will have access to the home user's directory in
> case you provide let's say ~/.ssh/id_rsa as argument. Another
> possibility would be to check the GIT_SSH_COMMAND env variable. I
> suppose you also need to make sure ssh is available for git-fetch.

Another way to use a private repo is oauth authentication.

(channel … (url "https://gitlab-ci-token:xxxxxxxxxxxxx-xxxxxx@gitlab.com/author/repository.git")

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-04-30 19:56 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 [this message]
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=875zqv5lh4.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=david.larsson@selfhosted.xyz \
    --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.