From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>,
Guix-devel <guix-devel@gnu.org>
Subject: Re: Lightning talk at IPFS camp
Date: Thu, 06 Jun 2019 14:36:12 +0200 [thread overview]
Message-ID: <87k1dygabn.fsf@ambrevar.xyz> (raw)
In-Reply-To: <m1zhmuyko1.fsf@ordinateur-de-catherine--konrad.home>
[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
> I was thinking of the Guix package definitions. In the long run,
> assuming IPFS turns out to be reliable enough, we could put all source
> into IPFS with a CID reference, rather then today's many ways to
> download source files.
There would be nothing special about it beside implementing an IPFS
fetcher, or would it? Let me know if I misunderstood.
> Again in the long run, if we don't mind depending on IPFS, we don't need
> the Guix store any more. Package installation would amount to local
> pinning. Anyone could then build a package anywhere (home directory,
> ...) and just add it to IPFS. Since that also eliminates the technical
> constraints of the store, the same mechanism could be used for any kind
> of data processing, with the results stored in IPFS. Reproducibility of
> any kind of computation via Guix, with building software just an
> important special case.
Very good point, I like it. I think I'll mention this in the talk.
> For human input, Git would be OK, with repositories stored in IPFS
> (there's already some support for that, see
> https://github.com/ipfs/go-ipld-git). A more radical redesign is
> Radicle (http://www.radicle.xyz/), which uses IPFS as a collaboration
> platform (still at the git level). I guess Radicle could be used for
> much more than that in Guix, but I haven't looked at that in detail.
Didn't know Radicle, it looks fantabulous! And... it uses (or plans to)
a Scheme-based language! :)
So you are saying that we could move the guix.git to a Radicle project,
right?
Makes sense to me.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-06-06 12:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 7:07 Lightning talk at IPFS camp Pierre Neidhardt
2019-05-31 22:10 ` Ludovic Courtès
2019-06-03 15:15 ` Konrad Hinsen
2019-06-03 16:19 ` Pronaip
2019-06-03 18:53 ` Konrad Hinsen
2019-06-06 8:13 ` Pierre Neidhardt
2019-06-06 12:15 ` Konrad Hinsen
2019-06-06 12:36 ` Pierre Neidhardt [this message]
2019-06-06 16:53 ` Konrad Hinsen
2019-06-07 12:39 ` Ludovic Courtès
2019-06-07 13:48 ` Konrad Hinsen
2019-06-07 20:10 ` Ludovic Courtès
2019-06-07 12:41 ` Ludovic Courtès
2019-06-07 13:45 ` Konrad Hinsen
2019-06-13 21:38 ` ng0
2019-06-24 20:37 ` Pierre Neidhardt
2019-06-26 12:19 ` Pierre Neidhardt
2019-06-27 14:53 ` Ludovic Courtès
2019-06-27 22:04 ` Pierre Neidhardt
2019-07-01 10:16 ` 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=87k1dygabn.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=konrad.hinsen@fastmail.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 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.