[Pkg-tcltk-commits] r257 - policy

[frankie at alioth.debian.org]

Author: frankie
Date: 2007-10-14 09:13:20 +0000 (Sun, 14 Oct 2007)
New Revision: 257

Modified:
   policy/tcltk-policy.sgml
Log:
Fixed for coherence with default pkgs introduction


Modified: policy/tcltk-policy.sgml
===================================================================
--- policy/tcltk-policy.sgml	2007-10-14 08:48:03 UTC (rev 256)
+++ policy/tcltk-policy.sgml	2007-10-14 09:13:20 UTC (rev 257)
@@ -330,7 +330,8 @@
 	  Programs that can run with any version of Tcl/Tk should be started
 	  with <tt>#!/usr/bin/tclsh</tt> or <tt>#!/usr/bin/wish</tt>.  
 	  They must also specify a dependency on <package>tclsh</package> or
-	  <package>wish</package> virtual packages. 
+	  <package>wish</package> virtual packages (deprecated) or on default 
+	  packages (better). 
 
 	  You're free to use <tt>#!/usr/bin/env tclsh</tt> and <tt>#!/usr/bin/env wish</tt>, 
 	  if you'd like to give the user a chance to override the Debian Tcl/Tk package with a
@@ -350,7 +351,8 @@
 
 	  Again, if you're using <tt>#!/usr/bin/env tclsh<var>X</var>.<var>Y</var></tt>, 
 	  or <tt>#!/usr/bin/env wish<var>X</var>.<var>Y</var></tt>
-	  please be aware that a user might override the Debian Tcl/Tk package with a local version.
+	  please be aware that a user might override the Debian Tcl/Tk packages with a local version
+	  and that release default packages can change also.
 	</p>
       </sect>
 
@@ -361,19 +363,29 @@
       <p>
 	Build dependencies for Tcl/Tk dependent packages must be
 	declared for every Tcl/Tk version, that the package is built
-	for. In order to build for a specific version, add the versioned
-	dependencies; there is currently no way to specify an
-	unversioned dependency, due to the lack of a proper Tcl/Tk default version.
+	for. In order to build for a specific version, add the versioned Tcl/Tk packages
+	dependencies; it is generally better depending on the appropriate default
+	packages with an eventual strict or relaxed versioning.
 
-	Architecture dependent packages must depend on the
-	<package>tcl<var>X</var>.<var>Y</var>-dev</package> package; 
-	for architecture independent
-	packages, it may be correct to depend on the
-	<package>tcl<var>X</var>.<var>Y</var></package>|.
+	Extension packages should depend appropriately on one or more of the 
+	following packages, for instance (with or without additional package version 
+	relationships):
+	<example>
+	tcl-dev
+	tk-dev
+	tclX.Y-dev
+	tkX.Y-dev
+	</example>
+	Module packages or script libraries should depend on the
+	<example>
+	tcl<var>X</var>.<var>Y</var>
+	tcl
+	tk<var>X</var>.<var>Y</var>
+	tk
+	</example>
+	Dependencies on the virtual packages
 	<package>tclsh</package> or 
-	<package>tk<var>X</var>.<var>Y</var></package>|.
-	<package>wish</package> respectively, where X.Y is the current stable Tcl/Tk
-	version.
+	<package>wish</package> respectively, are acceptable in Lenny, but deprecated.
       </p>
     </appendix>