[ntpsec-main commit] Explain why Perl scripts are not installed by default.

[Eric S. Raymond]

Module:    ntpsec-main
Branch:    master
Commit:    c04e4d0153e28637b85d78c0178cc724a835aa55
Changeset: http://git.ntpsec.org//commit/?id=c04e4d0153e28637b85d78c0178cc724a835aa55

Author:    Eric S. Raymond <esr at thyrsus.com>
Date:      Tue Nov  3 02:15:32 2015 -0500

Explain why  Perl scripts are not installed by default.

---

 INSTALL    | 12 ++++++++++++
 devel/TODO | 10 ----------
 2 files changed, 12 insertions(+), 10 deletions(-)

diff --git a/INSTALL b/INSTALL
index 67e429b..9dea68d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -133,6 +133,18 @@ By default, `make install' will install the package's files in
 installation prefix other than `/usr/local' by giving waf the
 option `--prefix=PATH'.
 
+== Uninstalled binaries and scripts ==
+
+Due to variations in Perl library paths, our stock source distribution
+makes no attempt to install certain Perl scripts: notably
+ntpleapfetch, ntpwait, and ntptrace.  If you installed this sotware
+from a binary package prepared by your OS distributor, the OS
+distributor may install them, arranging a rendezvous with the
+Perl implementation's library path.
+
+The utils/ directory contains various other uninstalled programs, some
+of only historical interest. Consult util/README for details.
+
 == Optional Features ==
 
 The waf builder accepts `--enable-FEATURE' options to where FEATURE
diff --git a/devel/TODO b/devel/TODO
index cad6c9e..c976557 100644
--- a/devel/TODO
+++ b/devel/TODO
@@ -7,16 +7,6 @@
 * The doc target should build manual pages. Model command is
   a2x --format manpage --asciidoc-opts=--conf-file=../docs/asciidoc.conf foo.txt
 
-* There's no installation yet for ntpleapfetch, or the Perl
-  executables that should be installed (ntpwait, ntptrace), nor
-  for their support library under perllib/.
-
-* We need to live-test leap seconds, both getting them from a file
-  with ntpleapfetch and getting them from other NTP servers.
-
-* ntpwait and ntptrace need to be smoke-tested on a live installation.
-  This would complete the list of installables known to be behaving sanely.
-
 * Unit testing.  "waf check" needs to run all the unit tests.
   This means both that the C++ glue needs to be fixed and waf needs
   to actually call the tests.