[Starkit] filleting tcllib

Steve Landers steve at DigitalSmarties.com
Wed May 4 20:59:28 CEST 2005


On 04/05/2005, at 7:56 PM, Steve Blinkhorn wrote:
>
> The trouble with text files is that they need maintaining, and an
> out-of-date text file just throws you back to manually working through
> the dependencies.   If you think about it, every script in tcllib that
> has dependencies has "package require" statements; there is already a
> top-level pkgIndex.tcl file which implicitly contains a list of
> packages and where they are located; each package has its own
> pkgIndex.tcl which details what to source.
>
> But there are some funnies.   autoproxy lives under http - there may
> be good sense in that, and it's simple to discover, but some of the
> location/dependency combinations are more obscure.   A good script
> taking advantage of the facilities of Tcl to walk recursively around
> collecting dependencies and putting them together would surely be
> prefereable to a manually-maintained text file?

Look for Don Porters "package package" as a starting point.

Steve

--
Steve Landers                     Software Design Solutions
Digital Smarties                  steve at DigitalSmarties.com
Perth, Western Australia          DigitalSmarties.com



More information about the Starkit mailing list