all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org, "Frederick M. Muriithi" <fredmanglis@protonmail.com>
Subject: Re: Using Guix archive (Help!)
Date: Sun, 7 Jan 2018 11:32:11 +0100	[thread overview]
Message-ID: <20180107103211.GA3362@thebird.nl> (raw)
In-Reply-To: <20180107091624.GA2981@thebird.nl>

> On Sat, Jan 06, 2018 at 01:46:18PM +0100, Ricardo Wurmus wrote:
> > >   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.

OK, the format is pretty simple. On why Nix did not use tar instead:

  https://lethalman.blogspot.nl/2014/08/nix-pill-9-automatic-runtime.html

I kind of like the way nar files work(ed) in Nix. No signing, no
assumptions. Much like tar. If we can view nar files and just add
their contents to the store we would have another powerful
distribution mechanism. Especially in controlled environments. At this
point I have to set up two publish servers just to pass packages
along. I have to tell others how to add a key and substitute URLs.

It is overkill. Also nar files can be one-click installs with or
without a store.

And for the record, I am no fan of signed binaries installs. Much of
the world does not require you to install a key first. When a user
installs software we can assume he knows what he is doing and trusts
the source (rightfully or not). Signing is good, but it should be
optional.

Same for a default Guix binary install. By installing Guix we trust
the source implicitely. But I a know I am heretic screaming into the
void ;). I'll scream once a year, nevertheless. I know screaming is
easy, so maybe I can help a little here.

I have limited internet these weeks, but when I have more space I can
look at Nix tooling again. See if there is something to view the
contents of a nar file. If we want to stick to NAR we can improve the
use of them. That would give Guix nar, pack, Docker and my relocatable
binary installs. Choice is good.

Pj.

  reply	other threads:[~2018-01-07 10:35 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 [this message]
2018-01-08 15:15       ` Tobias Geerinckx-Rice
2018-01-08 15:32         ` Pjotr Prins
2018-01-09 12:13   ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180107103211.GA3362@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=fredmanglis@protonmail.com \
    --cc=guix-devel@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.