diff options
Diffstat (limited to 'doc/handbook/chapters/developer.texi')
-rw-r--r-- | doc/handbook/chapters/developer.texi | 25 |
1 files changed, 13 insertions, 12 deletions
diff --git a/doc/handbook/chapters/developer.texi b/doc/handbook/chapters/developer.texi index a1b5583cb..cd81fcfb7 100644 --- a/doc/handbook/chapters/developer.texi +++ b/doc/handbook/chapters/developer.texi | |||
@@ -100,7 +100,7 @@ following links: | |||
100 | @itemize @bullet | 100 | @itemize @bullet |
101 | @item @xref{Top, Introduction,, gnunet-c-tutorial, The GNUnet C Tutorial}. | 101 | @item @xref{Top, Introduction,, gnunet-c-tutorial, The GNUnet C Tutorial}. |
102 | @c broken link | 102 | @c broken link |
103 | @c @item @uref{https://gnunet.org/git/gnunet.git/plain/doc/gnunet-c-tutorial.pdf, GNUnet C tutorial} | 103 | @c @item @uref{https://git.gnunet.org/gnunet.git/plain/doc/gnunet-c-tutorial.pdf, GNUnet C tutorial} |
104 | @item GNUnet Java tutorial | 104 | @item GNUnet Java tutorial |
105 | @end itemize | 105 | @end itemize |
106 | 106 | ||
@@ -124,7 +124,7 @@ The public subsystems on the GNUnet server that help developers are: | |||
124 | 124 | ||
125 | @item The version control system (git) keeps our code and enables | 125 | @item The version control system (git) keeps our code and enables |
126 | distributed development. | 126 | distributed development. |
127 | It is publicly accessible at @uref{https://gnunet.org/git/}. | 127 | It is publicly accessible at @uref{https://git.gnunet.org/}. |
128 | Only developers with write access can commit code, everyone else is | 128 | Only developers with write access can commit code, everyone else is |
129 | encouraged to submit patches to the GNUnet-developers mailinglist: | 129 | encouraged to submit patches to the GNUnet-developers mailinglist: |
130 | @uref{https://lists.gnu.org/mailman/listinfo/gnunet-developers, https://lists.gnu.org/mailman/listinfo/gnunet-developers} | 130 | @uref{https://lists.gnu.org/mailman/listinfo/gnunet-developers, https://lists.gnu.org/mailman/listinfo/gnunet-developers} |
@@ -133,14 +133,14 @@ encouraged to submit patches to the GNUnet-developers mailinglist: | |||
133 | We use it to track feature requests, open bug reports and their | 133 | We use it to track feature requests, open bug reports and their |
134 | resolutions. | 134 | resolutions. |
135 | It can be accessed at | 135 | It can be accessed at |
136 | @uref{https://gnunet.org/bugs/, https://gnunet.org/bugs/}. | 136 | @uref{https://bugs.gnunet.org/, https://bugs.gnunet.org/}. |
137 | Anyone can report bugs. | 137 | Anyone can report bugs. |
138 | 138 | ||
139 | @item Our site installation of the | 139 | @item Our site installation of the |
140 | Continuous Integration (CI) system @code{Buildbot} is used | 140 | Continuous Integration (CI) system @code{Buildbot} is used |
141 | to check GNUnet builds automatically on a range of platforms. | 141 | to check GNUnet builds automatically on a range of platforms. |
142 | The web interface of this CI is exposed at | 142 | The web interface of this CI is exposed at |
143 | @uref{https://gnunet.org/buildbot/, https://gnunet.org/buildbot/}. | 143 | @uref{https://old.gnunet.org/buildbot/, https://old.gnunet.org/buildbot/}. |
144 | Builds are triggered automatically 30 minutes after the last commit to | 144 | Builds are triggered automatically 30 minutes after the last commit to |
145 | our repository was made. | 145 | our repository was made. |
146 | 146 | ||
@@ -1098,7 +1098,7 @@ development of GNUnet services, command line tools, APIs and tests. | |||
1098 | First of all you have to obtain gnunet-ext from git: | 1098 | First of all you have to obtain gnunet-ext from git: |
1099 | 1099 | ||
1100 | @example | 1100 | @example |
1101 | git clone https://gnunet.org/git/gnunet-ext.git | 1101 | git clone https://git.gnunet.org/gnunet-ext.git |
1102 | @end example | 1102 | @end example |
1103 | 1103 | ||
1104 | The next step is to bootstrap and configure it. For configure you have to | 1104 | The next step is to bootstrap and configure it. For configure you have to |
@@ -1905,7 +1905,7 @@ topology where peer connectivity follows power law - new peers are | |||
1905 | connected with high probability to well connected peers. | 1905 | connected with high probability to well connected peers. |
1906 | (See Emergence of Scaling in Random Networks. Science 286, | 1906 | (See Emergence of Scaling in Random Networks. Science 286, |
1907 | 509-512, 1999 | 1907 | 509-512, 1999 |
1908 | (@uref{https://gnunet.org/git/bibliography.git/plain/docs/emergence_of_scaling_in_random_networks__barabasi_albert_science_286__1999.pdf, pdf})) | 1908 | (@uref{https://git.gnunet.org/bibliography.git/plain/docs/emergence_of_scaling_in_random_networks__barabasi_albert_science_286__1999.pdf, pdf})) |
1909 | 1909 | ||
1910 | @item @code{GNUNET_TESTBED_TOPOLOGY_FROM_FILE}: The topology information | 1910 | @item @code{GNUNET_TESTBED_TOPOLOGY_FROM_FILE}: The topology information |
1911 | is loaded from a file. The path to the file has to be given. | 1911 | is loaded from a file. The path to the file has to be given. |
@@ -2133,8 +2133,8 @@ To automate the GNUnet we created a set of automation tools to simplify | |||
2133 | the large-scale deployment. We provide you a set of scripts you can use | 2133 | the large-scale deployment. We provide you a set of scripts you can use |
2134 | to deploy GNUnet on a set of nodes and manage your installation. | 2134 | to deploy GNUnet on a set of nodes and manage your installation. |
2135 | 2135 | ||
2136 | Please also check @uref{https://gnunet.org/installation-fedora8-svn} and | 2136 | Please also check @uref{https://old.gnunet.org/installation-fedora8-svn} and |
2137 | @uref{https://gnunet.org/installation-fedora12-svn} to find detailed | 2137 | @uref{https://old.gnunet.org/installation-fedora12-svn} to find detailed |
2138 | instructions how to install GNUnet on a PlanetLab node. | 2138 | instructions how to install GNUnet on a PlanetLab node. |
2139 | 2139 | ||
2140 | 2140 | ||
@@ -2300,7 +2300,7 @@ subsystem. | |||
2300 | @subsubsection CORE must be started | 2300 | @subsubsection CORE must be started |
2301 | 2301 | ||
2302 | A uncomplicated issue is bug #3993 | 2302 | A uncomplicated issue is bug #3993 |
2303 | (@uref{https://gnunet.org/bugs/view.php?id=3993, https://gnunet.org/bugs/view.php?id=3993}): | 2303 | (@uref{https://bugs.gnunet.org/view.php?id=3993, https://bugs.gnunet.org/view.php?id=3993}): |
2304 | Your configuration MUST somehow ensure that for each peer the | 2304 | Your configuration MUST somehow ensure that for each peer the |
2305 | @code{CORE} service is started when the peer is setup, otherwise | 2305 | @code{CORE} service is started when the peer is setup, otherwise |
2306 | @code{TESTBED} may fail to connect peers when the topology is initialized, | 2306 | @code{TESTBED} may fail to connect peers when the topology is initialized, |
@@ -2747,7 +2747,8 @@ code. | |||
2747 | 2747 | ||
2748 | Since now activating DEBUG automatically makes it VERBOSE and activates | 2748 | Since now activating DEBUG automatically makes it VERBOSE and activates |
2749 | @strong{all} debug messages by default, you probably want to use the | 2749 | @strong{all} debug messages by default, you probably want to use the |
2750 | https://gnunet.org/logging functionality to filter only relevant messages. | 2750 | @uref{https://old.gnunet.org/logging, https://old.gnunet.org/logging} |
2751 | functionality to filter only relevant messages. | ||
2751 | A suitable configuration could be: | 2752 | A suitable configuration could be: |
2752 | 2753 | ||
2753 | @example | 2754 | @example |
@@ -8674,7 +8675,7 @@ eliminate the need to first create a directory. | |||
8674 | 8675 | ||
8675 | Collections are also advertised using @code{KSBlock}s. | 8676 | Collections are also advertised using @code{KSBlock}s. |
8676 | 8677 | ||
8677 | @c https://gnunet.org/sites/default/files/ecrs.pdf | 8678 | @c https://old.gnunet.org/sites/default/files/ecrs.pdf |
8678 | 8679 | ||
8679 | @node File-sharing persistence directory structure | 8680 | @node File-sharing persistence directory structure |
8680 | @subsection File-sharing persistence directory structure | 8681 | @subsection File-sharing persistence directory structure |
@@ -8794,7 +8795,7 @@ The gnunet-regex-profiler can be used to profile the usage of mesh/regex | |||
8794 | for a given set of regular expressions and strings. | 8795 | for a given set of regular expressions and strings. |
8795 | Mesh/regex allows you to announce your peer ID under a certain regex and | 8796 | Mesh/regex allows you to announce your peer ID under a certain regex and |
8796 | search for peers matching a particular regex using a string. | 8797 | search for peers matching a particular regex using a string. |
8797 | See @uref{https://gnunet.org/szengel2012ms, szengel2012ms} for a full | 8798 | See @uref{https://old.gnunet.org/szengel2012ms, szengel2012ms} for a full |
8798 | introduction. | 8799 | introduction. |
8799 | 8800 | ||
8800 | First of all, the regex profiler uses GNUnet testbed, thus all the | 8801 | First of all, the regex profiler uses GNUnet testbed, thus all the |