all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>,
	Gnunet Developers <gnunet-developers@gnu.org>
Subject: Re: gnunet-guile reboot & guix
Date: Sun, 14 Jan 2018 00:45:46 +0000	[thread overview]
Message-ID: <20180114004546.r7st2kprczcgqcdu@abyayala> (raw)
In-Reply-To: <87mv1hla2o.fsf@gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 1731 bytes --]

Ludovic Courtès transcribed 1.0K bytes:
> Hello,
> 
> Amirouche Boubekki <amirouche@hypermove.net> skribis:
> 
> > 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 need guix from today with latest guile-bytestructures 1.0.1.
> >
> > You can get the code using the following command:
> >
> >    git clone git://gnunet.org/gnunet-guile2.git
> 
> Thanks a lot for giving it some love!
> 
> Perhaps we should retire the repo at
> <https://git.savannah.gnu.org/cgit/guix/gnunet.git/>?
> (The ‘wip-monad’ branch might be of interest though.)
> 
> Ludo’.
> 
> _______________________________________________
> GNUnet-developers mailing list
> GNUnet-developers@gnu.org
> https://lists.gnu.org/mailman/listinfo/gnunet-developers

I think both Amirouche as well as myself (and gnunet.org) have a
copy of the old code base. If I understand savannah hosting
correctly 'retiring' just means making it read-only, so that
would be alright.
Development happens on gnunet.org and future releases will be
placed on the GNU Ftp folder of gnunet.

Our mailinglist at gnunet-developers is open for patches
(no sign-up required) and whoever wants to help developing
it can get push access (of course Amirouche has to decide on
this project, etc).

Eventually we should remove the old repository https://gnunet.org/git/gnunet-guile,
or rename the current one (gnunet-guile2).

That is my position. I'm not working on this right now,
Amirouche does.
-- 
ng0 :: https://ea.n0.is
A88C8ADD129828D7EAC02E52E22F9BBFEE348588 :: https://ea.n0.is/keys/

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 162 bytes --]

_______________________________________________
GNUnet-developers mailing list
GNUnet-developers@gnu.org
https://lists.gnu.org/mailman/listinfo/gnunet-developers

      reply	other threads:[~2018-01-14  0:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 21:23 gnunet-guile reboot & guix Amirouche Boubekki
2018-01-13  0:49 ` ng0
2018-01-13  9:26   ` Amirouche Boubekki
2018-01-13 11:14     ` ng0
2018-01-13 21:31 ` Ludovic Courtès
2018-01-14  0:45   ` ng0 [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180114004546.r7st2kprczcgqcdu@abyayala \
    --to=ng0@n0.is \
    --cc=gnunet-developers@gnu.org \
    --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 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.