File add_readme-tests.patch of Package tar.10814

diff -ruN a/Makefile.in b/Makefile.in
--- a/Makefile.in	2017-12-22 20:14:53.900579664 -0500
+++ b/Makefile.in	2017-12-22 20:21:21.363943130 -0500
@@ -122,7 +122,7 @@
 POST_UNINSTALL = :
 build_triplet = @build@
 host_triplet = @host@
-DIST_COMMON = $(srcdir)/Make.rules INSTALL NEWS README AUTHORS \
+DIST_COMMON = $(srcdir)/Make.rules INSTALL NEWS README README-tests AUTHORS \
 	ChangeLog THANKS $(srcdir)/Makefile.in $(srcdir)/Makefile.am \
 	$(top_srcdir)/configure $(am__configure_deps) \
 	$(srcdir)/config.h.in ABOUT-NLS COPYING TODO build-aux/ar-lib \
diff -ruN a/README-tests b/README-tests
--- a/README-tests	1969-12-31 19:00:00.000000000 -0500
+++ b/README-tests	2017-12-22 20:21:59.706691355 -0500
@@ -0,0 +1,22 @@
+Subpackage tar-tests
+====================
+
+The tar-tests package contains the testsuite which is included in tar sources.
+The testsuite is normally run during make phase (make check) and is also
+automatically run when the tar rpm is being build (in %check section of spec
+file).
+
+Normally, there is no reason to need the tar-tests package. It can however be
+used to verify, that tar functions properly in an installed system (e.g. to
+find issues in tar's dependencies, problems with incompatible libraries, etc.).
+
+Testsuite is installed into /var/lib/tests/tar
+
+To run the testsuite:
+
+cd /var/lib/tests/tar
+./testsuite --help # show options
+
+# needed for genfile binary used in tests
+./testsuite AUTOTEST_PATH=/var/lib/tests/tar/bin [other options]
+