From: Phil <phil@beadling.co.uk>
To: help-guix@gnu.org
Subject: guix pull only from private channel
Date: Tue, 15 Dec 2020 17:58:19 +0000 [thread overview]
Message-ID: <85czzbx878.fsf@beadling.co.uk> (raw)
Hi all,
Two things I can't find clarified anywhere - when doing a guix pull from a
private channel which provides supplementary packages to the standard
Guix channel.
1) If the private channel is a git repo accessed via ssh it seems
necessary to add the ssh key to an ssh-agent rather than have it pick up
~/.ssh/id_rsa. This isn't a huge problem but when the ssh key has no
passphrase the use of an agent is actually more complicated than passing
the key directly? Is it possible to specify a key file, and if not, is
there any good reason why not (I thought perhaps it might be access via
the guix-daemon or similar at a wild guess)?
2) Assuming I use an ssh-agent to avoid issue in 1), if I want to only
pull updates from my private channel and not from the Guix channel, I
find myself doing something like the below to force Guix channel to stay constant:
eval `ssh-agent` && ssh-add && guix pull --commit=$(guix describe -f
json | jq -r '.[] | select(.name=="guix").commit') && guix upgrade my-package-name
This works, but it feels rather ugly - is there an easier way of saying
"hold guix constant, but pull in latest updates from my private
channel" - it feels like a common use-case to me?
Thanks,
Phil.
next reply other threads:[~2020-12-15 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 17:58 Phil [this message]
2020-12-16 14:07 ` guix pull only from private channel zimoun
2020-12-19 12:28 ` Phil
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=85czzbx878.fsf@beadling.co.uk \
--to=phil@beadling.co.uk \
--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.
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).