[subversion-commit] SVN tex-common commit + diffs: r1674 - tex-common/trunk/doc

[Frank Küster]

Author: frank
Date: 2006-10-05 16:49:44 +0000 (Thu, 05 Oct 2006)
New Revision: 1674

Modified:
   tex-common/trunk/doc/Debian-TeX-Policy.pdf
   tex-common/trunk/doc/Debian-TeX-Policy.sgml
Log:
reindenting


Modified: tex-common/trunk/doc/Debian-TeX-Policy.pdf
===================================================================
(Binary files differ)

Modified: tex-common/trunk/doc/Debian-TeX-Policy.sgml
===================================================================
--- tex-common/trunk/doc/Debian-TeX-Policy.sgml	2006-10-05 16:48:48 UTC (rev 1673)
+++ tex-common/trunk/doc/Debian-TeX-Policy.sgml	2006-10-05 16:49:44 UTC (rev 1674)
@@ -915,18 +915,18 @@
 	<tt>build-depend</tt> on the TeX system</heading>
 	<sect1><heading>Configuration</heading>
 	  <p>
-	If packages that build-depend on the TeX system need a changed
-	configuration, they should not try to provide it statically.
-	If settings in any other configuration file are inappropriate
-	for a package to build, this is (usually) a bug in the package
-	that provides the file.  It should be fixed in this package,
-	not circumvented by a workaround in the build process.  Such
-	workarounds have proven to be problematic, because they might
-	stop working after changes in the depended-on package, and
-	such failure cannot be foreseen by its maintainers.  If a
-	change is still necessary, the package should use the
-	configuration update programs with the <tt>--outputdir</tt>
-	and <tt>--add-file</tt> options.
+	    If packages that build-depend on the TeX system need a changed
+	    configuration, they should not try to provide it statically.
+	    If settings in any other configuration file are inappropriate
+	    for a package to build, this is (usually) a bug in the package
+	    that provides the file.  It should be fixed in this package,
+	    not circumvented by a workaround in the build process.  Such
+	    workarounds have proven to be problematic, because they might
+	    stop working after changes in the depended-on package, and
+	    such failure cannot be foreseen by its maintainers.  If a
+	    change is still necessary, the package should use the
+	    configuration update programs with the <tt>--outputdir</tt>
+	    and <tt>--add-file</tt> options.
 	  </p>
 	</sect1>
 	<sect1><heading>Font cache data</heading>