From: Phil <phil@beadling.co.uk>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix pull only from private channel
Date: Sat, 19 Dec 2020 12:28:47 +0000 [thread overview]
Message-ID: <85bleqx9mo.fsf@beadling.co.uk> (raw)
In-Reply-To: <CAJ3okZ09urm3X2LhkGBXC83iCrTq-j-t+j-=mjYCAzY5SZvxkw@mail.gmail.com>
Thanks Simon - that helped!
zimoun writes:
> About this, you should write a specific channels.scm file and then run:
>
> guix pull -C channels.scm
>
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!
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.
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?
next prev parent reply other threads:[~2020-12-19 12:29 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 [this message]
2020-12-21 12:16 ` zimoun
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=85bleqx9mo.fsf@beadling.co.uk \
--to=phil@beadling.co.uk \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).