unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Phil <phil@beadling.co.uk>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix pull only from private channel
Date: Mon, 21 Dec 2020 13:16:10 +0100	[thread overview]
Message-ID: <86wnxb9wxh.fsf@gmail.com> (raw)
In-Reply-To: <85bleqx9mo.fsf@beadling.co.uk>

Hi,

On Sat, 19 Dec 2020 at 12:28, Phil <phil@beadling.co.uk> wrote:

> The bit I was missing was how do I create a channels file that keeps
> 'guix' at a constant commit - the scheme snippet you sent me is perfect, and
> gave me a good way-in to the API - thanks!

Do not take the snippet as bullet-proof.  It is a quick example to
illustrate the Guix power. ;-)


> One question - what's the reasoning about making all channel files have
> a guix channel?  Obviously it makes sense that there must be a guix
> channel referenced somewhere - but my expectation was (wrongly) that if
> I created a channel file with only my private channel in it, it would
> simply ignore guix and pull only what my private channel offered.  Instead it
> complains that there is no guix channel defined.

You mean that:

--8<---------------cut here---------------start------------->8---
$ cat /tmp/one-channel.scm
(list
 (channel
  (name 'past)
  (url "https://gitlab.inria.fr/guix-hpc/guix-past.git")))

$ guix pull -C /tmp/one-channel.scm -p /tmp/one
Updating channel 'past' from Git repository at 'https://gitlab.inria.fr/guix-hpc/guix-past.git'...
guix pull: warning: pulled channel 'past' from a mirror of https://gitlab.inria.fr/guix-hpc/guix-past, which might be stale
Building from this channel:
  past      https://gitlab.inria.fr/guix-hpc/guix-past.git	829923f
/tmp/one-channel.scm:2:1: error: 'guix' channel is lacking
hint: Make sure your list of channels contains one channel named `guix' providing the core of Guix.
--8<---------------cut here---------------end--------------->8---

Well, somehow you need one channel that provides the command “guix”.  It
is possible to cheat with a local clone and set url to “file:///path/to/clone”.

> I'm guessing it wants to weigh-up guix vs my private channel to pick the
> latest version of a package from either, but that doesn't make sense to
> me if I know that my private channel contains packages which are always
> mutually exclusive from the guix channel?

I am not sure to understand what you want to do, but you can pin one
“guix” version with something like:

--8<---------------cut here---------------start------------->8---
(list
 (channel
  (name 'past)
  (url "https://gitlab.inria.fr/guix-hpc/guix-past.git"))
 (channel
  (name 'guix) ; avoid to recompute heavy derivations and build modules
  (url "https://git.savannah.gnu.org/git/guix.git")
  (commit "d62c9b2671be55ae0305bebfda17b595f33797f2"))) ; v1.1.0
--8<---------------cut here---------------end--------------->8---


Hope that helps,
simon


  reply	other threads:[~2020-12-21 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15 17:58 guix pull only from private channel Phil
2020-12-16 14:07 ` zimoun
2020-12-19 12:28   ` Phil
2020-12-21 12:16     ` zimoun [this message]
2020-12-22  9:27       ` Phil
2020-12-22 11:44         ` zimoun

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=86wnxb9wxh.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=phil@beadling.co.uk \
    /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).