[Top][All Lists]

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

Re: [GNUnet-developers] GNU Guix GSoC ideas

From: Ling Kun
Subject: Re: [GNUnet-developers] GNU Guix GSoC ideas
Date: Tue, 26 Mar 2013 13:11:12 +0800


On Tue, Mar 26, 2013 at 2:11 AM, Ludovic Courtès <address@hidden> wrote:

Please find below project suggestions for GNU Guix for this year’s GSoC.


<h3 id="guix"><a href="" href="" target="_blank">">Guix</a></h3>

<p>GNU Guix is a purely functional package manager, and associated free
software distribution, for the GNU system.  In addition to standard
package management features, Guix supports transactional upgrades and
roll-backs, unprivileged package management, per-user profiles, and
garbage collection.</p>

<p><strong>Contact:</strong> address@hidden (to subscribe, see the
  <a href="" href="" target="_blank">">list-info page</a>).<br/>
<strong>Mentors:</strong> <a href="" href="mailto:address@hidden">address@hidden">Ludovic Court&egrave;s</a>

<h4>Supporting binary package distribution through GNUnet</h4>

GNU Guix provides a transparent binary/source deployment model.  A
server can claim: “hey, I have the binary for
<tt>/nix/store/v9zic07iar8w90zcy398r745w78a7lqs-emacs-24.3</tt>!”, where the
base32 string uniquely identifies a build process.  If you trust that
server to provide genuine binaries, then you can grab them instead of
building Emacs locally.

The “traditional model” has been to have a build farm build and serve
binary packages.  In that model, users trust the build farm to provide
authentic binaries.

The project aims to provide a <emph>practical</emph> decentralization
distribution mechanism for binary packages, using <a
href="" file sharing service</a>.  In that
model, users would be able to automatically share binaries they have
built locally, and to install binaries built by other users.  This is
part of a broader goal of <emph>disintermediation</emph> among users,
and between users and upstream software developers.

Problems to be solved <a
href="" href="" target="_blank">">include</a>
the authentication of binary packages, user privacy, and the development
of a user interface that makes it trivial to contribute package build


reply via email to

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