all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28699@debbugs.gnu.org
Subject: [bug#28699] [PATCH] pull: Add GUIX_PULL_URL environment variable.
Date: Fri, 06 Oct 2017 06:39:56 +0300	[thread overview]
Message-ID: <87a8152bcj.fsf@gmail.com> (raw)
In-Reply-To: <87o9pm7xk4.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 05 Oct 2017 11:28:59 +0200")

Hello Ludovic,

thanks for review!

ludo@gnu.org (Ludovic Courtès) writes:

> Oleg Pykhalov <go.wigust@gmail.com> skribis:
>
>> From 2638c08eef0e8c173111ced6bbc95167f6130fd7 Mon Sep 17 00:00:00 2001
>> From: Oleg Pykhalov <go.wigust@gmail.com>
>> Date: Wed, 4 Oct 2017 12:01:41 +0300
>> Subject: [PATCH] pull: Add GUIX_PULL_URL environment variable.
>>
>> * guix/scripts/pull.scm (%repository-url): Add GUIX_PULL_URL environment
>>   variable.
>> * doc/guix.texi (Invoking guix pull): Mention GUIX_PULL_URL.
>
> I’m not entirely convinced, especially with a look on “channels”, which
> would provide a way to persistently register repo URLs.

Interesting.  I didn't know about channels before you mention.

> OTOH, I see that it can be convenient in the short-term for someone
> using a repo other than the default one.
>
> Thoughts?

So, as we don't have channels yet, then I think it's a useful patch.
Because I cannot use 'guix pull --url=URL' when I use 'M-x guix pull' in
GNU Emacs.

  reply	other threads:[~2017-10-06  3:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04  9:05 [bug#28699] [PATCH] pull: Add GUIX_PULL_URL environment variable Oleg Pykhalov
2017-10-05  9:28 ` Ludovic Courtès
2017-10-06  3:39   ` Oleg Pykhalov [this message]
2017-10-07 20:41     ` bug#28699: " Ludovic Courtès

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=87a8152bcj.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=28699@debbugs.gnu.org \
    --cc=ludo@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.