Documentation polishing.

README

@@ -71,6 +71,8 @@ ntpfrob/::      The ntpfrob utility collects several small diagnostic
 ntptime/:: 	Directory containing a utility for reading and modifying
 		kernel parameters related to the local clock.
 
+packaging/::	Parts and guidance for distribution packagers.
+
 pylib/::	Installable Python helper classes for scripts.
 
 tests/::	Self-test code.

devel/README

@@ -25,9 +25,6 @@ make-tarball::
 ntpv5.txt::
 	Design notes towards NTPv5.
 
-packaging.txt::
-	Guidance for binary package builders.
-
 pre-release.txt::
 	A collection of ideas about testing before a release.
 

packaging/README.txt

-Packaging scripts go here
+== Packaging ==
+
+Packaging scripts go in this directory.
+
+Some general guidance for packagers can be found in packaging.txt
 
 Debian packaging metadata can be found at:
 https://github.com/rlaager/ntpsec-pkg

devel/packaging.txt → packaging/packaging.txt

@@ -63,11 +63,12 @@ has a pivot date and resolves incoming timestamps to the era that
 minimizes distance between now and the timestamp.  This procedure
 is part of the core protocol specification.
 
-An instance's pivot time is constructed from BUILD_EPOCH defined at configure
-time in config.h.  If BUILD_EPOCH is set to a known time then the binaries are
-reproducible.  By default the BUILD_EPOCH is the time when the last './waf
-configure' was run.  You can override the BUILD_EPOCH with '-waf --build-epoch'
-or using the SOURCE_DATE_EPOCH environment variable.
+An instance's pivot time is constructed from BUILD_EPOCH defined at
+configure time in config.h.  If BUILD_EPOCH is set to a known time
+then the binaries are reproducible.  By default the BUILD_EPOCH is the
+time when the last './waf configure' was run.  You can override the
+BUILD_EPOCH with '-waf --build-epoch' or using the SOURCE_DATE_EPOCH
+environment variable.
 
 More information on reproduceable builds is at:
 https://reproducible-builds.org/[https://reproducible-builds.org/]