Version 4 of Simple Tcl Archive Network

Updated 2004-09-10 15:10:23 by lwv

Or STAN for short is my attempt at a package installer and auto downloader.

  • Simple: If you want install a package, a single command (GUI to come) will do it for you.
  • Simple: If you want to start your own archive, all you need is a webserver and some files.
  • Tcl: It should work with Pure-Tcl 8.3+
  • Archive: Lots of packages available (about 20, for now)
  • Network: Archives point to each other. Forming a network where each publisher can maintain their own library of binaries and pure tcl software.

Once stan is installed you can just:

 stantool install somepackage

To install somepackage.

The current library holds a few packages already, namely stan, snack (windows/linux-i386/macosx), zlib (windows/linux-i386) and dict (windows/linux-i386). Additionally, a secondary (linked!) archive lists all the cantcl packages. Not all cantcl packages will install at the moment (because pkg_mkIndex doesn't work for them!).

-- 10Sept2004 PS

Getting stan

The simplest way to get started is to fetch the stantool.kit from [L1 ]. Alternatively, you can directly download http://pascal.scheffers.net/stan/stan/stan-0.9.tar.gz and http://pascal.scheffers.net/stan/stantool.tcl.txt . Stantool.tcl.txt requires that the package stan is already installed, whereas the kit is bundled with package stan. For the curious, take a peek at the directory listing too [L2 ].

Listing available packages:

 $ tclkit stantool.kit list

This will show all packages (supported by your platform!)

Installing:

 # tclkit stantool.kit install -libdir /usr/lib zlib

Will install zlib in /usr/lib/zlib-1.1

Getting some help:

 $ tclkit stantool.kit

If you use stantool outside tclkit, you will not have zlib available (Trf and the others are not supported yet). On unix platforms, this is not a big deal, as stan will try to use gzip, bzip2 and unzip. On windows you should really make your first stan command:

 c:\>tclsh stantool.tcl.txt install -libdir c:\tcl\lib zlib

Otherwise most packages will fail to install.

LV Great step forward! Question 1: when I do a stantool.kit list on my machine, I see two copies of vfs listed; however, there is no obvious difference between the two (the versions are the same). Also, it would really be helpful if the name column was as close to the commonly used name as possible - I see something listed as "soap" and "vfs" - are these really tclsoap and tclvfs? Question 2: is work proceeding to get cantcl and stan working better together? Question 3: does stan currently support the tcl module tip?

Category Application Category Deployment