[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ A ] [ B ] [ C ] [ D ] [ next ]

Debian Tcl/Tk Policy
Appendix D - Maintainer's Checklist

1. 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 package require ?-exact? Tcl X.Y or package require ?-exact? Tk X.Y, for instance. In those cases, use a versioned dependency on one of the default packages (tcl, tk, tcl-dev or tk-dev), e.g. tcl (>= X.Y). That is recommend instead of versioned packages dependencies, which are anyway supported for compatibility with past conventions. Note also that tk depends on tcl and tk-dev depends on tcl-dev.

2. Always install your package stuff in a per-package sub-directory of /usr/share/tcltk (for scripted modules) and/or /usr/lib/tcltk (for shared library extensions) along with the needed index file (see Tcl/Tk modules loading, Appendix B).

3. If your package supports multiarch install its index file into a subdirectory of /usr/lib/tcltk/$(DEB_HOST_MULTIARCH) directory. Tcl/Tk cannot determine multiarch triplet in runtime, so package indices for different architectures must differ.

4. This policy customizes auto_path differently with respect to generic upstream UNIX platforms, so that you should use preferably system provided tcl.m4. Occasionally that could either require custom hacks for non TEA-based building systems, or using --with-tcl or --with-tk argument for TEA scripts.

[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ A ] [ B ] [ C ] [ D ] [ next ]

Debian Tcl/Tk Policy