6 raco setup: Installation Management

► |  | raco: Racket Command-Line Tools

1 | raco make: Compiling Source to Bytecode
2 | raco exe: Creating Stand-Alone Executables
3 | raco distribute: Sharing Stand-Alone Executables
4 | raco planet: Automatic Package Distribution
5 | raco pkg: Package Management
6 | raco setup: Installation Management
7 | raco decompile: Decompiling Bytecode
8 | raco demod: Demodularizing Programs
9 | raco link: Library Collection Links
10 | raco pack: Packing Library Collections
11 | raco unpack: Unpacking Library Collections
12 | raco ctool: Working with C Code
13 | raco test: Run tests
14 | raco docs: Documentation Search
15 | raco expand: Macro Expansion
16 | raco read: Reading and Pretty-Printing
17 | raco scribble: Building Documentation
18 | Adding a raco Command
19 | Installation Configuration and Search Paths

▼ | 6 | raco setup: Installation Management

6.1 | Running raco setup
6.2 | Installing ".plt" Archives
6.3 | Controlling raco setup with "info.rkt" Files
6.4 | "info.rkt" File Format
6.5 | Package Dependency Checking
6.6 | API for Setup
6.7 | API for Installing ".plt" Archives
6.8 | API for Finding Installation Directories
6.9 | API for Reading "info.rkt" Files
6.10 | API for Relative Paths
6.11 | API for Collection Names
6.12 | API for Collection Searches
6.13 | API for Platform Specifications
6.14 | API for Cross-Platform Configuration
6.15 | API for Cross-References for Installed Manuals
6.16 | API for Materializing User-Specific Documentation
6.17 | Layered Installations
6.18 | Tethered Installations

top contents ← prev up next →

### 6`` raco setup: Installation Management🔗ℹ

The raco setup command builds bytecode, documentation, executables, and metadata indexes for all installed collections.

The collections that are built by raco setup can be part of the original Racket distribution, installed via the package manager (see Package Management in Racket), installed via PLaneT (see PLaneT: Automatic Package Distribution), linked via raco link, in a directory that is listed in the PLTCOLLECTS environment variable, or placed into one of the default collection directories.

The raco setup tool itself does not directly support the installation of collections, except through the now-discouraged -A flag (see Installing ".plt" Archives). The raco setup command is used by installation tools such as the package manager or PLaneT. Programmers who modify installed collections may find it useful to run raco setup as an alternative to un-installing and re-installing a set of collections.

6.1 Running raco setup
6.2 Installing ".plt" Archives
6.3 Controlling raco setup with "info.rkt" Files
6.4 "info.rkt" File Format
6.5 Package Dependency Checking
6.5.1 Declaring Build-Time Dependencies
6.5.2 How Dependency Checking Works
6.6 API for Setup
6.6.1 raco setup Unit
6.6.2 Options Unit
6.6.3 Options Signature
6.6.4 Setup Start Module
6.7 API for Installing ".plt" Archives
6.7.1 Non-GUI Installer
6.8 API for Finding Installation Directories
6.9 API for Reading "info.rkt" Files
6.10 API for Relative Paths
6.10.1 Representing Collection-Based Paths
6.10.2 Representing Paths Relative to "collects"
6.10.3 Representing Paths Relative to the Documentation
6.10.4 Displaying Paths Relative to a Common Root
6.11 API for Collection Names
6.12 API for Collection Searches
6.13 API for Platform Specifications
6.14 API for Cross-Platform Configuration
6.15 API for Cross-References for Installed Manuals
6.16 API for Materializing User-Specific Documentation
6.17 Layered Installations
6.18 Tethered Installations

top contents ← prev up next →