[Top][All Lists]

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

Re: ‘guix publish’ now compresses archives

From: Ricardo Wurmus
Subject: Re: ‘guix publish’ now compresses archives
Date: Tue, 19 Jul 2016 16:23:14 +0200
User-agent: mu4e 0.9.16; emacs 24.5.1

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

> Imagine situation where person A is running some distribution with
> Guix package manager on top and has some set of his personal packages
> containing additional patches which are not part of Guix GIT.
> He'd like to share the package with person B, running different
> distribution with Guix package manager at different revision on top,
> with different set of personal packages and alterations.
> I'd like to provide them a way, how to pass from person A to person B
> some binary archive in a way that he could understand (and verify)
> what he received. If it requries out-of-tree package definitions of
> person A, patches, etc, bundle it together.

This is already possible with “guix archive --export” and “--import”.

For the users at the MDC I wrote a little guide on how to share software
environments with other people so that others can reproduce the exact
same state.  The first way to share an environment is symbolic,
i.e. a manifest + Guix git hash + git hashes of any additional package

The second way to share an environment is the binary method.  With this
command you can export a complete profile (e.g. at
“/project/.guix-profile”) and write it to a gzipped archive:

guix archive --export --recursive \
  $(readlink -f /project/.guix-profile) | \
  gzip --stdout - > my-profile.nar.gz

The recipient can take this archive and import it into their store after
authenticating the public key of the sender.  The result of importing is
that a bunch of store items appear in the receiver’s Guix store.

Note that the package artifacts in the exported profile don’t have to be
the result of building packages from the package expressions in upstream
Guix.  They can include packages that were only defined in some
directory of GUIX_PACKAGE_PATH or that have been imported from another

What’s not so nice about this is that you can end up with binaries in
your store that you cannot rebuild yourself (because you never had the
sources to begin with).  (I wonder if this has implications on software

~~ Ricardo

reply via email to

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