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

[sgolovan-guest at alioth.debian.org]

Author: sgolovan-guest
Date: 2007-10-20 17:15:07 +0000 (Sat, 20 Oct 2007)
New Revision: 344

Modified:
   policy/trunk/tcltk-policy.sgml
Log:
[policy]
Fixed typos in appendix D.
Added a few examples to appendix B.


Modified: policy/trunk/tcltk-policy.sgml
===================================================================
--- policy/trunk/tcltk-policy.sgml	2007-10-20 16:59:41 UTC (rev 343)
+++ policy/trunk/tcltk-policy.sgml	2007-10-20 17:15:07 UTC (rev 344)
@@ -373,27 +373,47 @@
 	for. In order to build for a specific version, add the versioned Tcl/Tk packages
 	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 
-	following packages, for instance (with or without additional package version 
+      </p>
+      <p>
+	Extension packages and applications which link to Tcl/Tk libraries should depend
+	appropriately on one or more of the 
+	following packages (with or without additional package version 
 	relationships):
 	<example>
 	tcl-dev
 	tk-dev
-	tclX.Y-dev
-	tkX.Y-dev
+	tcl<var>X</var>.<var>Y</var>-dev
+	tk<var>X</var>.<var>Y</var>-dev
 	</example>
-	Module packages or script libraries should depend on the
+      </p>
+      <p>
+        For example, <package>tclreadline</package> build dependencies are the following:
 	<example>
+	Build-Depends: debhelper (>= 5.0.0), <var>tcl-dev</var>,
+	 libreadline5-dev, autotools-dev, quilt
+	</example>
+      </p>
+      <p>
+	Module packages, script libraries and Tcl-only applications should depend on the
+	<example>
+	tcl
+	tk
 	tcl<var>X</var>.<var>Y</var>
-	tcl
 	tk<var>X</var>.<var>Y</var>
-	tk
 	</example>
-	Dependencies on the virtual packages
+      </p>
+      <p>
+        For example, <package>tcllib</package> build dependencies are the following:
+	<example>
+	Build-Depends: debhelper (>= 5.0.0), quilt
+	Build-Depends-Indep: <var>tcl</var>
+	</example>
+      </p>
+      <p>
+	Do not use build dependencies on the virtual packages
 	<package>tclsh</package> or 
-	<package>wish</package> respectively, are acceptable in Lenny, but deprecated. Use
-	default packages instead.
+	<package>wish</package> as they cannot guarantee the same build environment.
+	Use default packages instead.
       </p>
     </appendix>
 
@@ -440,23 +460,23 @@
         Tcl/Tk has in general a very backward compatible API both at C and commands set levels.
 	When packaging a module or extension, verify if it requires a specific minimal version
 	and if it includes run-time checks about that, possibly (which is always convenient).
-	Scripts can include a <file>package require ?-strict? Tcl X.Y</file> or 
-	<file>package require ?-strict? Tk X.Y</file>, for instance.
+	Scripts can include a <file>package require ?-exact? Tcl X.Y</file> or 
+	<file>package require ?-exact? Tk X.Y</file>, for instance.
 	In those cases, use a versioned
-	dependency byi one of the default package (<file>tcl</file>, <file>tk</file>, <file>tcl-dev</file> or
-	<file>tk-dev</file>), e.g. <file>(tcl >=X.Y)</file>.
+	dependency on one of the default packages (<file>tcl</file>, <file>tk</file>, <file>tcl-dev</file> or
+	<file>tk-dev</file>), e.g. <file>tcl (>= X.Y)</file>.
 	That is recommend instead of versioned packages dependencies, which are anyway
 	supported for compatibility with past conventions. Note also that <file>tk</file>
 	depends on <file>tcl</file> and <file>tk-dev</file> depends on <file>tcl-dev</file>.
 	</item>
 	<item>
-	Install always your package stuff in a per-package sub-directory of
+	Always install your package stuff in a per-package sub-directory of
 	<file>/usr/share/tcltk</file> (for scripted modules) and/or <file>/usr/lib/tcltk</file> (for
-	shared library extensions) along with the needed index file (see <ref id="modules_loading">)
+	shared library extensions) along with the needed index file (see <ref id="modules_loading">).
 	</item>
 	<item>
-	This policy customizes <file>$auth_path</file> differently in respect with 
-	generic upstream <file>unix</file> platforms, so that you should use preferably 
+	This policy customizes <file>$auto_path</file> differently with respect to
+	generic upstream <file>UNIX</file> platforms, so that you should use preferably 
 	system provided <file>tcl.m4</file> or <file>tclConfig.sh</file>. Occasionally 
 	that could either require custom hacks for non TEA-based building systems, or 
 	using <file>--with-tcl</file> or <file>--with-tk</file> argument for TEA scripts.