[Pkg-tcltk-commits] r350 - policy/trunk

[frankie at alioth.debian.org]

Author: frankie
Date: 2007-10-21 09:05:49 +0000 (Sun, 21 Oct 2007)
New Revision: 350

Modified:
   policy/trunk/tcltk-policy.sgml
Log:
Fixed typo


Modified: policy/trunk/tcltk-policy.sgml
===================================================================
--- policy/trunk/tcltk-policy.sgml	2007-10-21 08:59:44 UTC (rev 349)
+++ policy/trunk/tcltk-policy.sgml	2007-10-21 09:05:49 UTC (rev 350)
@@ -79,11 +79,13 @@
 	  &wish; are provided by all source package versions 
 	  of Tcl and Tk. So pseudo-default Tcl and Tk exist, but they are generally a choice
 	  of the administrator by means of <tt>update-alternatives</tt> use.
-	  Starting from Lenny release, proper default packages are also provided,
-	  in order to manage modules and extensions packaging better.
+	  Starting from Lenny release, proper default packages are also provided by
+	  the Debian <file>tcltk-defaults</file> source package,
+	  in order to manage modules and extensions packaging and upgrading better.
 	  Modules should preferably use those packages when appropriate 
 	  (i.e. they are either version independent
-	  or properly versioned to inhibit the use of a non compatible versions), but it is
+	  or properly versioned to inhibit the use of a non compatible versions, 
+	  see <ref id="dependencies">), but it is
 	  not mandatory. This is consistent with the use of alternatives.
 	  The default packages are
 	  <example>
@@ -96,11 +98,13 @@
 	  </example>
 	</p>
 	<p>
-	  The default Debian Tcl/Tk version should alway be the latest stable
+	  The default Debian Tcl/Tk version should always be the latest stable
 	  upstream release that can be integrated in the distribution. Starting
 	  from 8.0, Tcl and Tk share the same version numbering. The default packages
 	  depend on the appropriate versioned packages and provide useful additional
-	  symlinks and alternatives.
+	  symlinks and alternatives. Default packages versions follow upstream versions,
+	  so that packages can use appropriate versioning constraints on them when
+	  it is needed.
 	</p>
 	<p>
 	  Apart from the default version, legacy versions of Tcl/Tk