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


Debian Tcl/Tk Policy
Chapter 2 - Packaged Modules


2.1 Module Names

Packages should be named by the primary module provided. The naming convention for a module foo is tcl-foo or tk-foo when the module is version independent.

The naming convention for a module foo is tclX.Y-foo or tkX.Y-foo when the module is version dependent.

If the package already uses the name tclfoo or tkfoo, that is, naming without Tcl/Tk versioning even if version-dependent and/or without hyphen, may use the name for now. However, the package naming proposed above is recommended for consistency.


2.2 Dependencies

Packaged modules available for one particular version of Tcl/Tk must depend on the corresponding libtclX.Y and/or libtkX.Y package if they don't contain Tcl/Tk scripts, and on tclX.Y and/or tkX.Y package if they do.

The recommended dependencies of version-independent packages are the following: If the package works in all available Tcl/Tk versions it should depend on libtcl or libtk (tcl or tk if it includes Tcl/Tk scripts). If the package works for several Tcl/Tk versions (but not for all) it should depend on all of them alternatively (e.g. libtcl8.5 | libtcl8.4).


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


Debian Tcl/Tk Policy

version 0.3.0

Francesco Paolo Lovergine frankie@debian.org
Sergei Golovan sgolovan@debian.org