unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Rémi Birot-Delrue" <asgeir@free.fr>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [GSoC] Supporting binary package distribution through GNUnet
Date: Wed, 25 Mar 2015 21:56:17 +0100	[thread overview]
Message-ID: <87mw30hk3y.fsf@gnu.org> (raw)
In-Reply-To: <87sicukybm.fsf@free.fr> ("Rémi Birot-Delrue"'s message of "Tue, 24 Mar 2015 20:08:45 +0100")

Hi!

Rémi Birot-Delrue <asgeir@free.fr> skribis:

> Ideally, would anyone be allowed to provide substitutes? Or would there
> be a set of “trusted substitute maintainers” (possibly one maintainer by
> package)? Maybe a mix. Maybe “answering this question” is part of the
> project?

IMO the basic trust model wouldn’t be much different from what we have
today (see
<https://www.gnu.org/software/guix/manual/guix.html#Substitutes>.)

That is, users would explicitly authorize certain providers by adding
their public key to their access control list (ACL.)

Now, many/most package builds are reproducible and should be
bit-identical.  So in practice, most of the time, a given build will be
actually be signed by several providers.

> Another point is: how would Guix handle these different sources? Should
> it propose the end-user a choice, or include a way to automatically
> choose in most cases?

To begin with, the ACL is enough.

> The prospect of having a (semi-)decentralised and Lisp-based
> package-manager is really appealing.

Glad you like it.  :-)

If you haven’t already, please have a look at the discussion with
Christian Grothoff on this list a few weeks ago for additional
thoughts.

I would also recommend that you get in touch with gnunet-developers or
#gnunet so they can tell you which GNUnet APIs to look at and provide
additional insight.  It would be nice if you could start playing with
GNUnet and Guix to become more familiar with them.

Also note that the deadline for student proposals is this Friday, so
make sure to post yours on Melange when you’re ready.

Thanks,
Ludo’.

      reply	other threads:[~2015-03-25 20:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 19:08 [GSoC] Supporting binary package distribution through GNUnet Rémi Birot-Delrue
2015-03-25 20:56 ` 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=87mw30hk3y.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=asgeir@free.fr \
    --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 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).