[Starkit] filleting tcllib

[Andreas Kupries]

> > I suppose what I am saying is that it's getting to the point with some
> > of our work where figuring out what to include is not so simple, but
> > considered use of the pkgIndex.tcl files and perhaps grep'ing for
> > package require lines might yield a tool of use to several if not
> > many (not limited just to tcllib, of course).
> >
> For tcllib, i think the best way would be to either add such information
> to the package documentation,

The [require] markup in doctools can help here, see all the Tcllib manpages,
but note that this can be out of sync with the sources. (And sak currently
does not crosscheck this with the sources. It can crosscheck pkgIndex and
sources. The option is 'validate'.

> so it can be automatically extracted or
> add it to the source and add an option to sak.tcl. The sak.tcl tool
> probably has some logic for things already, but thats Andreas Kupries
> domain...

Yep.

> IIRC the ActiveState helper apps for creating kits maintain some package
> description which includes dependencies...

The .tap files used by the Tcl Dev Kit currently do not contain dependency
information. And I am not sure about adding this, given that the tcl sources
already contain this (package require). It might be necessary for binary
packages where the Tcl_PkgRequire is not acessible to the tools.


--
	Andreas Kupries <andreask at ActiveState.com>
	Developer @ http://www.ActiveState.com, a division of Sophos
	Tel: +1 604 484 6491