1 ## Source code repository
3 You can get the latest development source code from our git
4 repository if you want to. This code may not work, run, or even
5 compile. You'll also *need* to have the latest versions of
6 autoconf, automake, libtool and gettext installed. The files that
7 can be generated using these tools are *not* in the repository.
9 ### Accessing the repository
11 You can [browse the repository](/git/tinc/) online. However, to
12 make real use of it you should have to have the git tools
13 installed. If you do not have them, you can find them at
14 [http://git.or.cz/](http://git.or.cz/).
15 Then run either one of these commands:
17 git clone git://tinc-vpn.org/tinc
21 git clone http://tinc-vpn.org/git/tinc
23 This creates a copy of the public repository of tinc. For every
24 release of tinc there is a corresponding tag in the git repository,
25 you can get an old version by running
26 `git checkout release-`*version* on your copy of the git
27 repository. If you have checked out a copy of the public
28 repository, you can bring it up to date using the command
33 There is also a clone of the official repository on GitHub:
35 [https://github.com/gsliepen/tinc](https://github.com/gsliepen/tinc)
37 You can use this to easily create your own forks and make your own commits public.
38 This allows us to review them and possibly merge them with the official tinc repository.
42 Whenever something is changed in the repository, a log message is
43 sent to the tinc-svn list. If you wish to be kept up to date, you
44 can subscribe yourself to that [[mailing list|mail]].