Héllo all, I restarted from scratch the gnunet-guile bindings. It was made much easier thanks to the work of ng0 on gnunet documentation and guile-bytestructures to handle C structs and unions. You
I’ve considered a solution for that: GNUnet allows one to create specific namespace and publish files under this namespace. Unlike publishing under the “global namespace” where keywords are use
Sree Harsha Totakura <address@hidden> skribis: Cross-posting is fine for this discussion, IMO. Yeah, let’s keep HTTP optional. The requirement will be to have a server over GNUnet’s MESH, right?
No problem; I was also following your thread on guix-devel. Let's just stick with the GNUnet server (we call such a server as a service in GNUnet, let's call it Guix service) as of now. HTTP can be d
Hello, address@hidden skribis: I think many of us dream of such a thing. :-) Unfortunately GNUnet hasn’t seen any release since April 2014, which I find worrying. It may be worth considering other
Since reproducible builds are a goal of Guix, as far as I know, maybe it would make sense to only do solution A, and only do it for packages which are reproducible. That would provide extra motivatio
Hi Im sorry for coming up with an update in the proposal for the binary distribution for GSoC 14 this late. I had my university exams. I hope the shortlisting is not already over and we can still con
Hi Im sorry for coming up with an update in the proposal for the binary distribution for GSoC 14 this late. I had my university exams. I hope the shortlisting is not already over and we can still con
Hi, This may have been due to my unclear communication at the Guix Meeting on Friday. What I said there is that we cannot possibly know the hash of the output *ahead of time*, which is why it cannot
Hi amirouche, amirouche <address@hidden> skribis: Before jumping to conclusions, did you check the narinfo format that we use on HTTP? A narinfo is essentially a statement that a given store item, re
Hello Guix! Here’s a little update. The current binary package distribution (through HTTP) is based on two components: a substituer (that retrieves packages) and a publisher. The current plan is to
Hi, This is a very interesting idea indeed! Thank you for the pointers. I've taken a quick look at the code Rémy created in 2015. I wonder if it's still working. Looks like there are a some tests, s
Hello, Maxim Cournoyer <address@hidden> skribis: Sure, I agree this is a worthwhile goal. If you haven’t already, check out the GSoC by Rémy Birot-Delrue on this topic a couple of years ago: https
Hi Rémi, Thanks for the update! So I can see two milestones now, as we discussed before: For that you can literally copy guix/scripts/publish.scm as a starting point, and simply remove the HTTP-rela
Hello! I’m happy to announce that Rémi Birot-Delrue will be working on binary package distribution for Guix using GNUnet as part of Google’s Summer of Code, as described at <http://www.gnu.org/s
Hi all, So far, I've summarized the info in a small roadmap I intend to follow Roadmap: (tuple(s) answers[see below for structure]). tests with static database. * work on a client-side binary list re
If the accumulation of signatures happens in the DHT, that's fine, but in that case, did you mean to write that in reply to the 'dht-get' request that you'd receive "a set of tuples" instead of "a tu
Mark H Weaver <address@hidden> skribis: Because as I view it, everyone would publish its own signature. Then, as a user, one can see all those signatures, which is a good thing for the reasons you me
Hi! I'd like this also to be mentioned briefly under the GNUnet project so that anyone interested in GNUnet can find it. Please add the following under GNUnet ideas: <h4>Supporting GNU Guix's package
Maxim Cournoyer transcribed 4.2K bytes: This week applications for university started, so I will transfer the documentation when I have more time. Probably within the next weeks. For just the system