Hi,
On Tue, 22 Dec 2020 at 09:27, Phil wrote:
> Yep this is what I've ended up doing - but am still a bit surprised that
> even with a pinned guix commit id, and a private channel containing a
> single trivial package with available substitute, doing a 'git pull' is
> still fairly expensive (app
zimoun writes:
> Hi,
>
> Do not take the snippet as bullet-proof. It is a quick example to
> illustrate the Guix power. ;-)
Yep understood - it was a good starting point for me to expand on!
> You mean that:
>
> $ guix pull -C /tmp/one-channel.scm -p /tmp/one
> /tmp/one-channel.scm:2:1: err
Hi,
On Sat, 19 Dec 2020 at 12:28, Phil 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 quic
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
Hi,
On Tue, 15 Dec 2020 at 19:29, Phil wrote:
> 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
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
