gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: updated gana scripts


From: gnunet
Subject: [taler-docs] branch master updated: updated gana scripts
Date: Mon, 31 Jul 2023 10:48:24 +0200

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 170b436b updated gana scripts
170b436b is described below

commit 170b436beefe96fd73c15ee49dc66a4e0e2e8a7c
Author: Florian Dold <florian@dold.me>
AuthorDate: Mon Jul 31 10:48:14 2023 +0200

    updated gana scripts
---
 taler-developer-manual.rst | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
index 2c4c1c37..b8858c0e 100644
--- a/taler-developer-manual.rst
+++ b/taler-developer-manual.rst
@@ -275,10 +275,9 @@ One common submodule is ``contrib/gana``, which pulls from 
the
 `GNUnet GANA repository <https://git.gnunet.org/gana.git/>`__.
 For example, in the
 `Taler exchange repository <https://git.taler.net/exchange.git>`__,
-the bootstrap script eventually runs the ``git submodule update`` command
-early on, and later runs script ``./contrib/gana.sh``, which in turn
-runs script ``./contrib/gana-update.sh``, which performs various tasks,
-such as generating the file ``src/include/taler_signatures.h``.
+the bootstrap script eventually runs the ``git submodule update --init`` 
command
+early on, and later runs script ``./contrib/gana-generate.sh``, which
+generates files such as ``src/include/taler_signatures.h``.
 
 Thus, to update that file, you need to:
 
@@ -290,8 +289,7 @@ Thus, to update that file, you need to:
 
 - Commit the change, and push it to the GANA Git repo.
 
-- (in Taler Repo) Change directory to ``contrib/gana`` and run
-  command ``git pull`` there.
+- (in Taler Repo) Run the ``contrib/gana-latest.sh`` script.
 
 - Bootstrap, configure, do ``make install``, ``make check``, etc.
   (Basically, make sure the change does not break anything.)

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]