From: ng0 <contact.ng0@cryptolab.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Debugging info unavailability
Date: Sat, 6 May 2017 12:46:43 +0000 [thread overview]
Message-ID: <20170506124643.u62fs4ptmi2acgkp@abyayala> (raw)
In-Reply-To: <CAN-vT6TXjCU1Mefgk8LOrjcA_En=AkSeGhyuVwJjNX=Yj-uLsA@mail.gmail.com>
Maxim Cournoyer transcribed 1.0K bytes:
…
> >> What good is a substitute server if it doesn't hold the stuff I need
> >> *now*? :) On the other side, it really makes me want to look at GNUnet,
> >> which seems like the better long term solution.
> >
> > Though GNUnet doesn’t solve the fact that one needs a lot of CPU and
> > storage to build and store all this. :-)
> >
>
> I think what I meant was "integration of GNUnet with guix publish".
> Something which would allow anyone to effortlessly share what's been
> built on their machine with the other Guix users. A zero config kind
> of thing, with auto discovery of peers and available substitutes.
>
> I haven't researched much about GNUnet yet, but it seems it might be
> fit for that purpose.
>
> Maxim
>
This has been addressed between 2013? and late 2015, and I'm about to document my own
discussions, thoughts, and roadmap for this (gathered in the last 2 years).
In the sense of freedom of choice, I'd rather make this an opt-in (contrary to what
my own position in discussions was before) so that I can make pragmaOS use this and
those who would like to use it too.
The main roadblocker is 5 weeks - 5 months until a new GNUnet release, but there's
some tasks to work on which can be quickly updated once we have released GNUnet 0.11
or which version number is decided upon.
If you are interested, I can CC you in the message update when I have documented
the ideas (though they are 90% identical to the outcomes of the GSoC discussions
of the past, thought about without knowing it has been discussed before).
My basic idea without going too much into depth (I don't want to search my papers):
- following the ideas of pragmaOS, to first make GNUnet as easy as
possible to use and configure (the system service I'm working on)
- update the gnunet-guile bindings for HEAD of gnunet but work with 0.10.1 for the
current version of the service
- write the necessary guix integrations
There's more documented with reasons and ideas beyond just this.
I'm often quoted as the GNUnet expert here in Guix recently (as far as I follow
irc logs), but I would really appreciate if interested people who are passionate
about seeing this feature implemented would join me.
I'm just slow because one person efforts are always slow when the entire project
is not just writing the above listed project but also 3 concepts (blueprint for
how to build a system based on GuixSD, create a base for future systems, package
and write all the things which are required by the blueprint system (which happens
to be focused on GNUnet applications), and last but not least improve the system
by helping upstream).
I know from the meeting december of last year that Ludovic is sceptic about
GNUnet by now to some degree, and if I could decide on releases GNUnet would now
have an -dev or -preview or whatever release. The amount of bugfixes which happened
since 0.10.1 are just too much to keep 0.10.1 around, especially since the compability
no longer works between nodes running 0.10.1 and ones running HEAD.
So far all we can is either take on the last two bugs (I don't know enough C) or
wait until Christian had time to work on them.
--
https://pragmatique.xyz
PGP: https://people.pragmatique.xyz/ng0/
next prev parent reply other threads:[~2017-05-06 12:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 0:02 Debugging info unavailability Danny Milosavljevic
2017-04-24 7:35 ` Tomas Cech
2017-05-02 10:08 ` Ludovic Courtès
2017-05-02 16:39 ` Maxim Cournoyer
2017-05-02 21:16 ` Ludovic Courtès
2017-05-03 4:53 ` Maxim Cournoyer
2017-05-03 6:29 ` Ricardo Wurmus
2017-05-03 10:11 ` Ludovic Courtès
2017-05-03 15:22 ` Maxim Cournoyer
2017-05-05 20:31 ` Ludovic Courtès
2017-05-05 21:47 ` Ricardo Wurmus
2017-05-06 12:21 ` Ludovic Courtès
2017-05-05 22:09 ` Maxim Cournoyer
2017-05-06 12:26 ` Distributing substitutes over GNUnet Ludovic Courtès
2017-05-11 15:05 ` Maxim Cournoyer
2017-05-06 12:46 ` ng0 [this message]
2017-05-11 5:13 ` Debugging info unavailability Maxim Cournoyer
2017-05-11 16:50 ` ng0
2017-05-11 21:04 ` 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
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=20170506124643.u62fs4ptmi2acgkp@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).