This teacup subcommand brings your locally-installed packages up to date, including fetching those packages that you don't have. Only fetches packages that can be used with Tcl installations it knows about.
Note that the current teacup has the following options that work with teacup update
DKF: If you cancel the update by pressing Control-C while it is running, you may need to use teacup regenerate to fix things before you can update again.
LV: I find that if I have a slow internet connection (less than 56k), large items seldom update in teacup update. I daily see errors such as:
Retrieving application base-tcl-thread 8.6.0.0.287710 solaris2.8-sparc ...@ http://teapot.activestate.com ... Error: Bad transfer: Size mismatch, expected '2776291', received '2179031'. MD5 mismatch, expected 'a5f4e8e0fadfd4292f7d99a1cdc77ebd', received '4c2e09516c57aba35f6d3879bf1d0f19'.
Most frustrating is when it is the cached INDEX that generates this error.
Mho frustration II:
C:\Dokumente und Einstellungen\Arbeit1>teacup update Retrieving package activestate::activetcl::demos 8.4 win32-ix86 ...@ http://teapot.activestate.com ... Error: Bad transf er: Size mismatch, expected '5681134', received '3960791'. MD5 mismatch, expected 'ed7f1d408ceb05295d45c8dadc63cf92', re ceived '677795078f56cfdeff044088eaf26921'. Installed 0 newer packages Installed 0 unknown packages C:\Dokumente und Einstellungen\Arbeit1>
Don't know how to work around this.
AK: What do you get as the result of 'teacup timeout' ? It seems as if only about 4 of 5 MB is transfered, and a timeout in the http package could cause that. MHo I already switched off timeout via teacup timeout -1...
[LV[ I've seen similar situations for several years now.