taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit cb2a8e96ce4467da6ff21f607922ceb2618a9823
parent df1fecf0954b831e59b906f0aad3b9e3c9d8f494
Author: Christian Grothoff <christian@grothoff.org>
Date:   Thu, 31 Dec 2020 20:15:10 +0100

explain how to create Debian packages in dev guide

Diffstat:
Mdevelopers-manual.rst | 27+++++++++++++++++++++++++++
1 file changed, 27 insertions(+), 0 deletions(-)

diff --git a/developers-manual.rst b/developers-manual.rst @@ -613,6 +613,33 @@ Directive file: Upload the files in **binary mode** to the ftp servers. +Creating Debian packages +------------------------ + +Our general setup is based on +https://wiki.debian.org/DebianRepository/SetupWithReprepro + +First, update at least the version of the Debian package in +debian/changelog, and then run: + +$ dpkg-buildpackage -rfakeroot -b -uc -us + +in the respective source directory (GNUnet, exchange, merchant) to create the +".deb" files. Note that they will be created in the parent directory. This +can be done on gv.taler.net, or on another (secure) machine. + +Next, the "*.deb" files should be copied to gv.taler.net, say to +``/root/incoming``. Then, go to ``/var/www/repos/apt/debian/`` and run +``reprepro includedeb sid /root/incoming/*.deb`` to import all Debian files +from ``/root/incoming/`` into the ``sid`` distribution. If Debian packages +were build against other distributions, reprepro may need to be first +configured for those and the import command updated accordingly. + +Finally, make sure to clean up ``/root/incoming/`` (by deleting the +now imported "*.deb" files). + + + Continuous integration ======================