| 1 | |
|---|
| 2 | NOTE: The CVS repository for NTP is inactive. NTP is now maintained |
|---|
| 3 | using BitKeeper; see README.bk for more info. |
|---|
| 4 | |
|---|
| 5 | To get the NTP distribution via anonymous CVS: |
|---|
| 6 | |
|---|
| 7 | % cvs -d :pserver:anoncvs@www.ntp.org:/cvs/ntp login |
|---|
| 8 | |
|---|
| 9 | the password is: anoncvs |
|---|
| 10 | |
|---|
| 11 | % rm -rf ntp |
|---|
| 12 | % cvs -d :pserver:anoncvs@www.ntp.org:/cvs/ntp co ntp |
|---|
| 13 | |
|---|
| 14 | after which the "ntp_update" script in the top-level of the tree should |
|---|
| 15 | keep things in synch and properly timestamped. |
|---|
| 16 | |
|---|
| 17 | PLEASE NOTE: |
|---|
| 18 | |
|---|
| 19 | When obtaining the NTP distribution directly via CVS instead of |
|---|
| 20 | using "ntp_update", the files are installed in an arbitrary |
|---|
| 21 | order. |
|---|
| 22 | |
|---|
| 23 | When you run "make", this may cause some of the generated files |
|---|
| 24 | to be reconstructed. |
|---|
| 25 | |
|---|
| 26 | If you do not have the right verison of automake and autoconf, |
|---|
| 27 | these files will be regenerated incorrectly. |
|---|
| 28 | |
|---|
| 29 | In this case, you can "fix" your distribution by running: |
|---|
| 30 | |
|---|
| 31 | ntp_update -C |
|---|
| 32 | |
|---|
| 33 | which will force any local changes to your NTP files to be |
|---|
| 34 | discarded and replaced with the versions in the repository. |
|---|
| 35 | |
|---|
| 36 | If "ntp_update -C" does not work just remove the "broken" |
|---|
| 37 | files (probably Makefile.in files) and re-run ntp_udate. |
|---|
| 38 | |
|---|
| 39 | There are some mailing lists for the NTP CVS distribution. For more |
|---|
| 40 | information, send a message to <majordomo@ntp.org> with the word "lists" |
|---|
| 41 | in the body of the message. |
|---|
| 42 | |
|---|
| 43 | If you get NTP via CVS, you MAY need to build the release using GNU make |
|---|
| 44 | and gcc. |
|---|
| 45 | |
|---|
| 46 | You can then "make dist" to build a release tarball that does not require |
|---|
| 47 | GNU make or gcc. |
|---|
| 48 | |
|---|
| 49 | The reason GNU make and gcc may be required is because the repository |
|---|
| 50 | version of NTP does not have the make dependencies built-in. These |
|---|
| 51 | dependencies are created dynamically, and this dynamic process may |
|---|
| 52 | require GNU make and gcc. |
|---|
| 53 | |
|---|
| 54 | I'm told that the version of automake we are now using does not require |
|---|
| 55 | GNU make or gcc for the dependency tracking, but I haven't tested this |
|---|
| 56 | yet. |
|---|
