Re: ‘guix publish’ now compresses archives

["Tomáš Čech" <tcech@suse.com>]

[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]

On Tue, Jul 19, 2016 at 04:23:14PM +0200, Ricardo Wurmus wrote:
>
>Tomáš Čech <sleep_walker@gnu.org> 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”.
> ...
>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
>freedom.)
>
>~~ Ricardo
>

Ooops, I answered to Ricardo only...

Yes, you can take exported archive (optionally with it's dependencies
- --recursive) and add it to the person B's store. That is comparable
to tarball (and making Guix aware of new items in store).

The thing that you can't rebuild the binaries is exactly my point,
because person A knows how to build it, but person B does not. Thanks!

S_W

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]