unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix support in cachix
Date: Fri, 13 Jul 2018 13:31:25 +0000	[thread overview]
Message-ID: <20180713133125.jr5rqxpdwmdwkijp@abyayala> (raw)
In-Reply-To: <87lgaim3kz.fsf@gnu.org>

Ludovic Courtès transcribed 540 bytes:
> Hello,
> 
> Marius Bakke <mbakke@fastmail.com> skribis:
> 
> > It looks useful for those who don't want to or can't publish their own
> > substitutes.  And `guix challenge` makes it easy to verify the builds
> > coming from a particular "channel".
> 
> I agree that it can be useful.
> 
> I would very much like it if we had a solution that did not rely on a
> central service, though.  If ‘guix publish’ could publish over
> BitTorrent, say (or GNUnet, like we tried during GSoC a few years ago),
> that would be awesome.

Let me interject for a second:
while I think work towards GNUnet makes sense (I haven't stopped following
my plan; going beyond just substitutes via FS),
we have some problems in GNUnet which need to be resolved first before
you can throw something at its FS. We have upcoming changes to FS in
the predictable near future after the 0.11 release which hopefully start
addressing changes we need in FS.
In the meantime, not trying to derail: amz3 did really good work with
the new Guile bindings for gnunet. Is anyone up to taking the bindings
further? If you would like to but you are having trouble setting up
either the bindings or gnunet itself for hacking, contact us and
we will be able to work something out. I can give you git access to
this repo. Even documenting it more than right now will be a big win
for other guile hackers!

Since my impression over the years was that Guix wants to embrace a
pluralism of distribution methods and not be fixed on one or two
ways to do it: writing integrations for bittorrent, ipfs, or whatever
could lead to fragmentation and while I technically don't really see
the point, it could be done. not every existing solution will work
in every location, but worst case we are getting some nice guile
bindings for other applications out of it ;)

> Thanks,
> Ludo’.
> 

      reply	other threads:[~2018-07-13 13:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 16:49 Guix support in cachix Oleg Pykhalov
2018-07-03 21:51 ` Ludovic Courtès
2018-07-04 14:17   ` Marius Bakke
2018-07-11 11:09     ` Ludovic Courtès
2018-07-13 13:31       ` Nils Gillmann [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=20180713133125.jr5rqxpdwmdwkijp@abyayala \
    --to=ng0@n0.is \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).