GNU bug report logs - #53775
[PATCH] gnu: Add gnunet-scheme

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 53775 in the body.
You can then email your comments to 53775 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: guix-patches <at> gnu.org
Subject: [PATCH] gnu: Add gnunet-scheme
Date: Fri, 04 Feb 2022 12:47:17 +0100

[Message part 1 (text/plain, inline)]

X-Debbugs-CC: pukkamustard <pukkamustard <at> posteo.net>, pukkamustard <pukkamustard <at> posteo.net>

[CC'ing pukkamustard and ludo for their interest in Guix+GNUnet]

Hi,

The first patch adds a module to guile-fibers required by gnunet-scheme.  It has been submitted upstream at <https://github.com/wingo/fibers/pull/50>, but there has not been any response so far.

The second commit adds 'gnunet-scheme', which is not the same as guile-gnunet:

"This package provides Guile modules for connecting to the NSE (network
size estimation) and DHT (distributed hash table) services of GNUnet.  It also
has infrastructure for writing new GNUnet services and connecting to them and
can be used from multi-threaded environments.  It is not to be confused with
@code{guile-gnunet} -- @code{guile-gnunet} supports a different set of services."

gnunet-scheme supports the DHT and NSE, while guile-gnunet doesn't.
Conversely, guile-gnunet supports FS while gnunet-scheme doesn't (yet).
Additionally, while it's not impossible per se, guile-gnunet is hard
to use from a multi-threaded context.

Next step: integrate it with guile-eris and the substituter patches based
on guile-eris (currently these only support IPFS as P2P backend)!

'guix lint gnunet-scheme guile-fibers' only have a single complaint:

gnu/packages/gnunet.scm:379:12: gnunet-scheme <at> 0.2: URI https://git.gnunet.org/git/gnunet-scheme.git not reachable: 404 ("Not Found")

"guix build gnunet-scheme" could download the source code though,
so I don't understand.

It fails to cross-compile because guile-fibers fails to cross-compile:

> checking for guile-3.0... yes
> checking for guile-3.0... no
> checking for guile3.0... no
> checking for guile-3... no
> checking for guile3... no
> checking for guile... no
> configure: error: guile required but not found

That's unrelated to gnunet-scheme though.

Greetings,
Maxime

[0001-gnu-guile-fibers-Add-fibers-io-wakeup.patch (text/x-patch, attachment)]

[0002-gnu-Add-gnunet-scheme.patch (text/x-patch, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 53775-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Maxime Devos <maximedevos <at> telenet.be>
Cc: 53775-done <at> debbugs.gnu.org, pukkamustard <pukkamustard <at> posteo.net>
Subject: Re: bug#53775: [PATCH] gnu: Add gnunet-scheme
Date: Fri, 04 Feb 2022 23:40:25 +0100

Hi,

Maxime Devos <maximedevos <at> telenet.be> skribis:

> The first patch adds a module to guile-fibers required by gnunet-scheme.  It has been submitted upstream at <https://github.com/wingo/fibers/pull/50>, but there has not been any response so far.

OK.

> The second commit adds 'gnunet-scheme', which is not the same as guile-gnunet:
>
> "This package provides Guile modules for connecting to the NSE (network
> size estimation) and DHT (distributed hash table) services of GNUnet.  It also
> has infrastructure for writing new GNUnet services and connecting to them and
> can be used from multi-threaded environments.  It is not to be confused with
> @code{guile-gnunet} -- @code{guile-gnunet} supports a different set of services."
>
> gnunet-scheme supports the DHT and NSE, while guile-gnunet doesn't.
> Conversely, guile-gnunet supports FS while gnunet-scheme doesn't (yet).
> Additionally, while it's not impossible per se, guile-gnunet is hard
> to use from a multi-threaded context.

Interesting.

> Next step: integrate it with guile-eris and the substituter patches based
> on guile-eris (currently these only support IPFS as P2P backend)!

Yay!

> 'guix lint gnunet-scheme guile-fibers' only have a single complaint:
>
> gnu/packages/gnunet.scm:379:12: gnunet-scheme <at> 0.2: URI https://git.gnunet.org/git/gnunet-scheme.git not reachable: 404 ("Not Found")
>
> "guix build gnunet-scheme" could download the source code though,
> so I don't understand.

I suppose Git doesn’t attempt to GET /index.html, contrary to the URL
probing code we have.

> From 8272cceae8642ed89eb3ebc110821a395f3ae087 Mon Sep 17 00:00:00 2001
> From: Maxime Devos <maximedevos <at> telenet.be>
> Date: Fri, 4 Feb 2022 11:16:46 +0000
> Subject: [PATCH 1/2] gnu: guile-fibers: Add (fibers io-wakeup).
>
> This patch is required by gnunet-scheme.  It has been submitted upstream at
> <https://github.com/wingo/fibers/pull/50>, but there has not been any response
> so far.
>
> * gnu/packages/patches/guile-fibers-wait-for-io-readiness.patch: New file.
> * gnu/packages/guile-xyz.scm (guile-fibers-1.1)[source]{patches}: Add it.
> * gnu/local.mk (dist_patch_DATA): Add it.

[...]

> From 5b57cdbb8f4d56c66885ea029cbe0a185d61a725 Mon Sep 17 00:00:00 2001
> From: Maxime Devos <maximedevos <at> telenet.be>
> Date: Fri, 4 Feb 2022 11:23:36 +0000
> Subject: [PATCH 2/2] gnu: Add gnunet-scheme.
>
> This is not the same as guile-gnunet, see the description.
>
> * gnu/packages/gnunet.scm (gnunet-scheme): New variable.

Applied both patches, thanks!

> +              ;; XXX: Work-around
> +              ;; <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49623>,
> +              ;; this can be removed once Guile > 3.0.7 is released.
> +              (snippet '(substitute* '("gnu/gnunet/config/parser.scm"
> +                                       "tests/config-parser.scm")
> +                          (("#\\{\\$\\{\\}\\}#") "#{${;};}#")
> +                          (("#\\{\\$\\{:-\\}\\}#") "#{${;:-};}#")
> +                          (("#\\{\\$\\{\\}\\}# #\\{\\$\\{:-\\}\\}#")
> +                           "#{$\\x7b;\\x7d;}# #{$\\x7b;:-\\x7d;}#")
> +                          (("'#\\{\\$\\{\\}\\}# '#\\{\\$\\{:-\\}\\}#")
> +                           "'#{$\\x7b;\\x7d;}# '#{$\\x7b;:-\\x7d;}#")))))

Wonderful, you deserve a prize for this one.  :-)

> +                         texmacs

I was surprised by the choice of TeXmacs for documentation—TeXmacs is a
beautiful piece of software, but I find it inconvenient that the manual
is only viewable as PDF, cannot link to other manuals, etc.  My 2¢.

(I was also surprised by the use of the (gnu gnunet) name space instead
of just (gnunet), say.)

Anyway, this looks exciting, thank you!

Ludo’.

Message #13 received at 53775 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: 53775 <at> debbugs.gnu.org
Cc: ludo <at> gnu.org
Subject: Re: bug#53775: closed (Re: bug#53775: [PATCH] gnu: Add gnunet-scheme)
Date: Sat, 05 Feb 2022 00:18:20 +0100

[Message part 1 (text/plain, inline)]

GNU bug Tracking System schreef op vr 04-02-2022 om 22:41 [+0000]:
> > +                         texmacs
> 
> I was surprised by the choice of TeXmacs for documentation—TeXmacs is
> a beautiful piece of software, but I find it inconvenient that the
> manual is only viewable as PDF, cannot link to other manuals, etc. 
> My 2¢.

Even with the disadvantages of TeXmacs over TeXinfo (no .info export
so not readable with info readers, no system for cross-references
between manuals except for direct hyperlinking ...), I still prefer
TeXmacs because its editor is just so convenient to use.

FWIW, TeXmacs not only has a PDF export, but also a HTML export:
$ $FAVOURITE_BROWSER $(guix build gnunet-scheme)/share/doc/scheme-gnunet/scheme-gnunet.html

Would be nice if TeXmacs gained some TeXinfo-style cross-referencing macros
and an '.info' export though ...

> (I was also surprised by the use of the (gnu gnunet) name space
> instead of just (gnunet), say.)

https://git.savannah.gnu.org/cgit/guix/gnunet.git/tree/ used (gnu
gnunet ...), so does gnunet-scheme.

The convention in Guileland seems to be (gnunet ...) though
(unlike, say, coffeeland where tld.domain.foo.bar is the convention),
so perhaps that will be corrected in a future version.

Greetings,
Maxime.

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.