| 1 | In order to use the BitKeeper repository version of NTP you will have |
|---|
| 2 | to have the following tools installed: |
|---|
| 3 | |
|---|
| 4 | autoconf 2.50 or later (we use 2.52) |
|---|
| 5 | automake (we use 1.5) |
|---|
| 6 | lynx |
|---|
| 7 | |
|---|
| 8 | Lynx is used to generate the COPYRIGHT file. Don't ask. |
|---|
| 9 | |
|---|
| 10 | You can get bitkeeper by visiting: |
|---|
| 11 | |
|---|
| 12 | http://www.bitkeeper.com/ |
|---|
| 13 | |
|---|
| 14 | We are using bitkeeper under their free license program. You can use |
|---|
| 15 | bitkeeper for free to access NTP, too. If you have questions about this, |
|---|
| 16 | please ask. The license is pretty easy to read. |
|---|
| 17 | |
|---|
| 18 | Once you have installed bitkeeper, you can clone any NTP repository. |
|---|
| 19 | |
|---|
| 20 | You can get the ntp-stable repository by either of the following commands: |
|---|
| 21 | |
|---|
| 22 | bk clone bk://www.ntp.org/home/bk/ntp-stable ntp-stable |
|---|
| 23 | |
|---|
| 24 | bk clone bk://ntp.bkserver.net/ntp-stable ntp-stable |
|---|
| 25 | |
|---|
| 26 | You can get the ntp-dev repository by either of the following commands: |
|---|
| 27 | |
|---|
| 28 | bk clone bk://www.ntp.org/home/bk/ntp-dev ntp-dev |
|---|
| 29 | |
|---|
| 30 | bk clone bk://ntp.bkserver.net/ntp-dev ntp-dev |
|---|
| 31 | |
|---|
| 32 | The IPV6 patch has been applied: |
|---|
| 33 | |
|---|
| 34 | bk clone bk://www.ntp.org/home/bk/ntp-dev-ipv6 ntp-dev-ipv6 |
|---|
| 35 | |
|---|
| 36 | bk clone bk://ntp.bkserver.net/ntp-dev-ipv6 ntp-dev-ipv6 |
|---|
| 37 | |
|---|
| 38 | The ntp-dev-ipv6 repository will be merged back in to the ntp-dev repo |
|---|
| 39 | as soon as the code is stable. |
|---|
| 40 | |
|---|
| 41 | If you are stuck behind a firewall that blocks access to the default port |
|---|
| 42 | used by bitkeeper (14690) but you can use port 80 instead, you can use |
|---|
| 43 | http as a bk transport mechanism. Just use: |
|---|
| 44 | |
|---|
| 45 | bk clone http://ntp.bkserver.net/REPO REPO |
|---|
| 46 | |
|---|
| 47 | Finally, it's possible to use SMTP as a bk transport mechanism. So far, we |
|---|
| 48 | haven't tried this. |
|---|
| 49 | |
|---|
| 50 | Once you have obtained the sources, do the following: |
|---|
| 51 | |
|---|
| 52 | cd REPO |
|---|
| 53 | bk -r edit to check out the files |
|---|
| 54 | autoreconf -f -i generates configure and Makefile.in's |
|---|
| 55 | |
|---|
| 56 | and you should be ready to go. You will get some warning messages from |
|---|
| 57 | autoreconf. Ignore these messages. |
|---|
| 58 | |
|---|
| 59 | You can update your repository by incanting: |
|---|
| 60 | |
|---|
| 61 | cd REPO |
|---|
| 62 | bk pull |
|---|
