unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, "Frederick M. Muriithi" <fredmanglis@protonmail.com>
Subject: Re: Using Guix archive (Help!)
Date: Tue, 09 Jan 2018 13:13:36 +0100	[thread overview]
Message-ID: <87h8rvut5b.fsf@gnu.org> (raw)
In-Reply-To: <878tdb40kl.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 06 Jan 2018 13:46:18 +0100")

Hello!

Ricardo Wurmus <rekado@elephly.net> skribis:

>> somehow propagated-inputs don't go into the archive. You'd think they are critical
>> dependencies.
>>
>>   Q1: is that to be expected?
>
> I’m not sure, but it seems wrong.

I understand it’s weird, but it’s expected: ‘guix archive’ is a
low-level thing that works at the store level.  Propagated inputs are a
package-level concept, so it doesn’t know about it.

>> NAR files are signed. I think it would be very useful to be able to
>> distribute unsigned NAR files.
>>
>>   Q2: can signing/checking be made optional?

No, on purpose.

However unsigned archives would be useful for content-addressed items
(e.g., source code downloads), and it’s currently not supported.

>>   Q3: how do we view the contents of a NAR file without unpacking it?
>
> I don’t think you can.  It’s a custom format implemented by
> nix/libutil/archive.cc.

It’s also implemented in (guix nar).  :-)

So it Wouldn’t Be Hard to implement a content browsers and support “guix
archive -t”.

Ludo’.

      parent reply	other threads:[~2018-01-09 12:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 11:08 Using Guix archive (Help!) Pjotr Prins
2018-01-06  6:04 ` Pjotr Prins
2018-01-06 12:46 ` Ricardo Wurmus
2018-01-07  9:16   ` Pjotr Prins
2018-01-07 10:32     ` Pjotr Prins
2018-01-08 15:15       ` Tobias Geerinckx-Rice
2018-01-08 15:32         ` Pjotr Prins
2018-01-09 12:13   ` Ludovic Courtès [this message]

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=87h8rvut5b.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=fredmanglis@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).