[Pkg-tcltk-commits] r264 - policy

frankie at alioth.debian.org frankie at alioth.debian.org
Mon Oct 15 10:29:15 UTC 2007


Author: frankie
Date: 2007-10-15 10:29:15 +0000 (Mon, 15 Oct 2007)
New Revision: 264

Modified:
   policy/tcltk-policy.sgml
Log:
Fixed typos and more changes for consistency about default packages.


Modified: policy/tcltk-policy.sgml
===================================================================
--- policy/tcltk-policy.sgml	2007-10-14 19:50:24 UTC (rev 263)
+++ policy/tcltk-policy.sgml	2007-10-15 10:29:15 UTC (rev 264)
@@ -63,11 +63,11 @@
 	  <package>wish</package> are provided by different 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
+	  Starting from Lenny release, proper default packages are also provided,
 	  in order to manage better modules and extensions packaging. 
-	  Modules should preferibly use those packages when appropriate 
-	  (i.e. they are version independent
-	  or properly versioned to inhibit the use of a non compatible versions), but it is 
+	  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
 	  not mandatory. This is consistent with the use of alternatives.
 	  The default packages are
 	  <example>
@@ -86,7 +86,7 @@
 	  must depend on the right versioned packages and provide useful additional
 	  symlinks and alternatives. At some point in the development cycle 
 	  after Lenny release, virtual packages could be dropped and all packages
-	  have to depend on default packages and/or versioned ones.
+	  have to only depend on default packages or versioned ones.
 	</p>
 	<p>
 	  Apart from the default version, legacy versions of Tcl/Tk
@@ -138,7 +138,8 @@
 	  core modules and extensions of the upstream Tcl/Tk distribution. 
 	  Any Tcl packages will include a <var>Provides:</var> item of the virtual package 
 	  <package>tclsh</package> and any Tk packages will include a <var>Provides:</var> 
-	  item for the <package>wish</package> virtual package.
+	  item for the <package>wish</package> virtual package. Those virtual packages
+	  could be dropped any time after Lenny release.
 	  They will also provide alternatives for the following files: 
 	  <package>/usr/bin/tclsh</package>
 	  <package>/usr/bin/wish</package>
@@ -169,7 +170,8 @@
 	    Tcl/Tk scripts that only work with a specific Tcl/Tk version must
 	    explicitely use the versioned interpreter name
 	    (<file>tclsh<var>X</var>.<var>Y</var></file> and/or <file>wish<var>X</var>.<var>Y</var></file>)
-	    and depend on the specific Tcl/Tk versioned package.
+	    and either depend on the specific Tcl/Tk versioned package or add versioning to their
+	    dependencies on the default Tcl/Tk packages.
           </p>
         </sect1>
         <sect1 id="interpreter_loc">
@@ -189,13 +191,14 @@
 	    possibility to override the Debian Tcl interpreter, he
 	    may want to use <file>/usr/bin/env tclsh</file> or
 	    <file>/usr/bin/env tclshX.Y</file>. The same consideration
-	    applies for Tk and the wish interpreter.
+	    applies for Tk and the wish interpreter. Administrators could also
+	    override default versions of the interpreters 
+	    using <tt>update-alternatives</tt>,
+	    so maintainers must always consider that the default Tcl/Tk 
+	    interpreters could be altered by administrators, so packages
+	    should always require a compatible version to avoid issues,
+	    when appropriate.
 	  </p>
-	  <p>
-	    The maintainer must always consider that the default Tcl/Tk version
-	    could be altered by administrators in the transition period
-	    to default packages.
-	  </p>
         </sect1>
       </sect>
 
@@ -228,6 +231,8 @@
 	  /usr/include/tcl -> /usr/include/tclX.Y
 	  /usr/include/tk -> /usr/include/tclX.Y
 	  </example>
+	  See net section and <ref id="debian_oddities"> for more information about 
+	  possible issues with extension building due to Debian customizations.
         </p>
       </sect>
 
@@ -265,7 +270,7 @@
 	the paths above consistently. See <ref id="modules_loading"> also for more information 
 	about Tcl/Tk specific ways of dealing with modules and extensions loading.
 	Developers must consider that these defaults impact TEA-based modules and use
-	preferibly system-wide <file>tcl.m4</file> and <file>tclConfig.sh</file> instead
+	preferably system-wide <file>tcl.m4</file> and <file>tclConfig.sh</file> instead
 	of private ones (see <ref id="debian_oddities">).
 	</p>
 
@@ -314,10 +319,14 @@
 	  <package>tk<var>X</var>.<var>Y</var></package> 
 	  package. They can depend on both the default version and
 	  the virtual <package>tclsh</package> or <package>tk</package>
-	  packages when they are version independent.
+	  packages when they are version independent. Those virtual packages
+	  could be dropped after Lenny release, so their use is deprecated.
 	  Due to limitations in current autobuild daemon
 	  it is mandatory to prepend a preferred Tcl/Tk version before each of the virtual packages.
-	  The preferred version should correspond to the current stable Tcl/Tk.
+	  The preferred version should correspond to the current default Tcl/Tk.
+	  Preferably packaged modules should instead depend on the default tcl and tk packages with
+	  or without version relationships when appropriate. This is the recommended dependency
+	  style.
 	</p>
       </sect>
 
@@ -364,7 +373,7 @@
 	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 Tcl/Tk packages
-	dependencies; it is generally better depending on the appropriate default
+	dependencies; it is generally better and recommended depending on the appropriate default
 	packages with an eventual strict or relaxed versioning.
 
 	Extension packages should depend appropriately on one or more of the 
@@ -385,7 +394,8 @@
 	</example>
 	Dependencies on the virtual packages
 	<package>tclsh</package> or 
-	<package>wish</package> respectively, are acceptable in Lenny, but deprecated.
+	<package>wish</package> respectively, are acceptable in Lenny, but deprecated. Use
+	default packages instead.
       </p>
     </appendix>
 




More information about the Pkg-tcltk-commits mailing list