restinside.blogg.se

1. #DO I NEED ACTIVESTATE ACTIVETCL INSTALL#
2. #DO I NEED ACTIVESTATE ACTIVETCL UPDATE#
3. #DO I NEED ACTIVESTATE ACTIVETCL CODE#

This command sets or queries which installation is the default installation repository. Prints either the list of shells the repository at dir is connected to, or the list of repositories the shell is using. Note that it is allowed to specify an arbitrary number of shells and repository dirs, inĪrbitrary order. Repository when a package is required, and teacup will not check the shell anymore when Removes the connection between the installation repository at dir and the tcl shell. Will ask the shell for the list of all packages it can use whenĬhecking if a package is already installed.

#DO I NEED ACTIVESTATE ACTIVETCL INSTALL#

Shell's platform before attempting to install a package, and it Means that teacup will accept only packages compatible with the Package is required, and the repository records the shell's location and platform information. The installation repository at dir when a This command is executed, the shell will search teacup linkĬreate a connection between the installation repository at dir and the tcl shell. To break the connections to all shells using the repository beforeĭeleting it from the filesystem. This command deletes the local installation (Note the space between "Application" and "Support"). Is specified then a platform-specific standard location is This command creates a local installation This command takes the path to a valid Tcl shellĪnd then adds the appropriate code, enabling it to look for and use Repositories, most Tcl shells, especially self-built ones, do not. While ActiveTcl's tcl shell comes already prepared with all theĬode necessary to be able to look for and use installation One of these repositories will be the defaultĭestination for doing package installations. Installation (repositories) are the repositories packages are The commands for doing so, and where thisĬonfiguration is stored, are explained in the section Configuration Ways for the environment it is in, with the settings persistingĪcross invocations. The behaviour of the application can be configured in various The set of archives when A is also the destination for packages to Makes no sense whatsoever to put an installation repository A into Installation A should be drawn from a different installation B. Installation repository to the set of archives known to teacup this makes sense only when packages for an Note however that while the above makes it possible to add an For local repositories both opaque and transparent repositories are Please see the section Management of archives Which are repositories to search when the TEApot client is asked to Options when having to deal with installation Please see the section Management of installation repositoriesįor the teacup commands relevant to theirĭirect management, and the option -at in See also the TEApot FAQ for more information. For other installations, the relevant codeĬan installed by using teacup's setup method.

#DO I NEED ACTIVESTATE ACTIVETCL CODE#

Necessary code is already part of the tclsh's " init.tcl". Require' to load a package from the repository. Installations, like ActiveTcl, which allow one to invoke 'package Repositories will be the default destination for doing packageĪn installation repository is one source of packages for Tcl On the one side are the installation repositories, whichĪre the repositories packages are installed into. It will also be used by administrators to manageĬentralized installations, if so desired.Īs such it sits squarely between two distinct sets of TEApot

This tool is used to manage a user's personal TEApot Purge ? -keep-last n? -keep-since timestamp? -at dir? Show ? -l|-last n? -s|-since timestamp? -at dir? teacup keys ? -v? -timeout sec? -http-proxy host: port? -at-default? -at dir?.teacup search ? -v? -timeout sec? -http-proxy host: port? -at-default? -at dir? -as csv| profile| table? query.teacup profiles ? -v? -timeout sec? -http-proxy host: port? -at-default? -at dir?.teacup get ? -v? -timeout sec? -http-proxy host: port? -at-default? -at dir? -is entity? -output outdir? name ? version ? architecture?.teacup list ? -v? -timeout sec? -http-proxy host: port? -all-platforms? -at-default? -at dir? -is entity? -as csv| profile| table? -only uninstalled| newer| unknown| update? name ? version?.teacup describe ? -v? -timeout sec? -http-proxy host: port? -at-default? -at dir? -is entity? -all? name ? version ? arch?.

#DO I NEED ACTIVESTATE ACTIVETCL UPDATE#

teacup update ? -v? -timeout sec? -http-proxy host: port? -dry-run? -only uninstalled| newer| unknown| update? -at dir?.teacup remove ? -dry-run? -at dir? -is entity? name ? version ? architecture?.