[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ‘guix publish’ now compresses archives

From: Ludovic Courtès
Subject: Re: ‘guix publish’ now compresses archives
Date: Tue, 19 Jul 2016 15:15:38 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

Hello Tomáš,

Tomáš Čech <address@hidden> skribis:

> As I am happy to see enthusiasm about Guix, I don't think that current
> archive format is usable for distribution of binary packages of
> whatever origin. Problem is that we have package definition as part of
> package manager GIT snapshot or local files but this information is
> not distributed along with the package archive.

I’m not sure what you mean.  The “substitute” mechanism is meant as a
cache.  Guix locally compiles the package recipe to a low-level
representation of the build process (a derivation), and then, it can
*optionally* ask substitute servers whether they have the result
corresponding to that derivation.

A derivation is self-contained and unambiguous.  I can do:

--8<---------------cut here---------------start------------->8---
$ guix build -d sed
$ cat $(guix build -d sed) | cut -d ']' -f 1
$ wget -O /tmp/sed-binary.nar.bz2
--2016-07-19 15:09:02--
Ni solvigas (, 
Konektado al (||:443... 
HTTP peto sendita, ni atendas respondon... 200 OK
Grando: nespecifita [application/x-nix-archive]
Ni konservas al: '/tmp/sed-binary.nar.bz2'

/tmp/sed-binary.nar     [ <=>                ] 145.07K  --.-KB/s    in 0.07s   

2016-07-19 15:09:02 (2.04 MB/s) - '/tmp/sed-binary.nar.bz2' konservita [148549]
--8<---------------cut here---------------end--------------->8---

… and now I have the binary corresponds to that sed-4.2.2.drv, or so
claims  (This URL scheme is what ‘guix publish’

Thus, does not need to know about the (package …)
form, the Git revision of Guix, whether the recipe was local or not,

Of course I have to trust to genuinely serve
binaries resulting corresponding to the derivations.  To express this
trust, I register its archive signing key, as explained at

Does that clarify things, or am I misunderstanding?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]