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

[frankie at alioth.debian.org]

Author: frankie
Date: 2007-10-19 15:45:02 +0000 (Fri, 19 Oct 2007)
New Revision: 323

Modified:
   policy/trunk/tcltk-policy.sgml
Log:
Introducing first suggestions in check-list


Modified: policy/trunk/tcltk-policy.sgml
===================================================================
--- policy/trunk/tcltk-policy.sgml	2007-10-19 12:53:12 UTC (rev 322)
+++ policy/trunk/tcltk-policy.sgml	2007-10-19 15:45:02 UTC (rev 323)
@@ -9,7 +9,7 @@
     <author>
 	<name>Sergei Golovan</name>
     </author>
-    <version>version 0.1.0</version>
+    <version>version 0.2.0</version>
 
     <abstract>
       This document describes the packaging of Tcl/Tk within the Debian
@@ -17,8 +17,6 @@
       and packages. This policy has been defined during Lenny release
       cycle, so pre-Lenny releases can violate this policy in one or 
       more aspects. Backporters are warned.
-
-      THIS IS A DRAFT DOCUMENT, NOT AN OFFICIAL POLICY.
     </abstract>
 
     <copyright>
@@ -436,9 +434,39 @@
 
     <appendix id="check_list">
       <heading>Maintainer's Checklist</heading>
-      <p>
-      TO BE DONE.
-      </p>
+      <enumlist>
+      	<item>
+        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.
+	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>.
+	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
+	<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">)
+	</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 
+	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.
+	</item>
+	<item>
+	Current policy still allows administrators to change default <file>tclsh</file> and
+	<file>wish</file> interpreters to different versions. Your packaged modules
+	and extensions should always be able to cope with that, and eventually to complain and 
+	terminate nicely.
+	</item>
+      </enumlist>
     </appendix>