kernel-netlink: Allow blank source address in routes for passthrough policies

[thirdparty/strongswan.git] / HACKING

diff --git a/HACKING b/HACKING
index 3a7a2c94d0407797f405c6ffab836bfafa02ddc9..b691e205a8e6990ce7e13951ba31d6d789c39e4c 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -1,30 +1,37 @@
-                 -------------------------
-                  strongSwan - Development
-                 -------------------------
+                ------------------------
+                strongSwan - Development
+                ------------------------
 
-Subversion repository
+Git repository
 ---------------------
 
-For interested developers, we have a public repository. To check out and 
-compile the code, you need the following tools:
+For interested developers, we have a public repository. To check out and compile
+the code, you need the following tools:
 
-    - Subversion (1.3.1)
-    - a recent GNU C complier (gcc-3.4.6)
-    - recent autotools (autoconf-2.59, automake-1.9.6, libtool-1.5.22)
-    - the usual strongSwan dependencies (gmp >= 4.1.4, optional curl, ldap)
-    - perl (5.8.8)
-    - lex (flex-2.5.33)
-    - yacc (bison-2.1)
-    - gperf (3.0.1)
-    - Doxygen (1.4.6)
+    - Git
+    - a recent GNU C compiler (>= 3.x)
+    - automake
+    - autoconf
+    - libtool
+    - pkg-config
+    - gettext
+    - perl
+    - python
+    - lex/flex
+    - yacc/bison
+    - gperf
 
-The numbers in brackets represent the versions used on our development systems,
-other version MAY work, too. Not all tools are checked by the configure script,
-as they are not needed in the tarball distributions, so check them manually.
+    Optionally:
+    - lcov/genhtml
+    - Doxygen
 
-To check out the trunk, use:
+To check out the master branch, use:
 
-    svn co http://www.strongswan.org/ikev2/trunk strongswan
+    git clone git://git.strongswan.org/strongswan.git
+
+or using HTTP:
+
+    git clone https://git.strongswan.org/strongswan.git
 
 After a successful check out, give the autotools a try:
 
@@ -40,20 +47,16 @@ Then you're in, start the build as usual:
 
 API documentation
 -----------------
-Charon and libstrongswan contain inline code documentation. These comments can be
-extracted using doxygen. It is built using 'make apidoc', which creates an 'apidoc'
-folder containing the HTML files.
 
+Charon and libstrongswan contain inline code documentation. These comments can
+be extracted using doxygen. It is built using 'make apidoc', which creates an
+'apidoc' folder containing the HTML files.
 
-uClibc support
---------------
+strongSwan wiki
+---------------
 
-To run strongSwan on uClibc, you need at least:
+A wiki for users and developers, including ticket system and source browser
+is available at
 
-String and Stdio Support --->
-  [*] Support glibc's register_printf_function()
-General Library Settings --->
-  [*] Support global constructors and destructors
+    https://wiki.strongswan.org
 
-It is fairly untested yet, so don't except to get it running without
-further tweaks.