From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: Debugging info unavailability Date: Sat, 6 May 2017 12:46:43 +0000 Message-ID: <20170506124643.u62fs4ptmi2acgkp@abyayala> References: <20170423020206.41aac1a2@scratchpost.org> <87d1brk1ul.fsf@gnu.org> <87shknnrfm.fsf@gmail.com> <87pofr0xjs.fsf@gnu.org> <87zieu7d8n.fsf@gmail.com> <87bmrah2s3.fsf@elephly.net> <87tw52uu51.fsf@gnu.org> <87r3066k4c.fsf@gmail.com> <87efw3yrj3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39013) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d6z6t-00061J-5C for guix-devel@gnu.org; Sat, 06 May 2017 08:46:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d6z6o-0004Ck-RC for guix-devel@gnu.org; Sat, 06 May 2017 08:46:55 -0400 Content-Disposition: inline In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Maxim Cournoyer Cc: guix-devel Maxim Cournoyer transcribed 1.0K bytes: =E2=80=A6 > >> 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 GNUn= et, > >> which seems like the better long term solution. > > > > Though GNUnet doesn=E2=80=99t solve the fact that one needs a lot of = CPU and > > storage to build and store all this. :-) > > >=20 > 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. >=20 > I haven't researched much about GNUnet yet, but it seems it might be > fit for that purpose. >=20 > Maxim >=20 This has been addressed between 2013? and late 2015, and I'm about to doc= ument 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 (contra= ry to what my own position in discussions was before) so that I can make pragmaOS us= e this and those who would like to use it too. The main roadblocker is 5 weeks - 5 months until a new GNUnet release, bu= t 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 doc= umented the ideas (though they are 90% identical to the outcomes of the GSoC disc= ussions 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 m= y 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 pas= sionate 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 (bluepri= nt 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 (whic= h 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 abo= ut GNUnet by now to some degree, and if I could decide on releases GNUnet wo= uld now have an -dev or -preview or whatever release. The amount of bugfixes whic= h happened since 0.10.1 are just too much to keep 0.10.1 around, especially since th= e 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 enoug= h C) or wait until Christian had time to work on them. --=20 https://pragmatique.xyz PGP: https://people.pragmatique.xyz/ng0/