Jay McCarthy <[email protected]>
The Racket package manager lets you install new libraries and collections, and the Racket package catalog helps other Racket programmers find libraries that you make available.
1 Getting Started with Packages
1.1 What is a Package?
1.2 Inspecting Your Installation
1.3 Finding Packages
1.4 Installing Packages
1.5 Updating Packages
1.6 Removing Packages
1.7 Creating Packages
1.7.1 Automatic Creation
1.7.2 Manual Creation
1.7.3 Linking and Developing New Packages
1.8 Sharing Packages
1.8.1 GitHub Deployment
1.8.2 Manual Deployment
1.8.3 Helping Others Discover Your Package
1.8.4 Naming and Designing Packages
1.8.5 Packages Compatible with Racket 5.3.5 and 5.3.6
1.8.5.1 Version Exceptions
2 Package Concepts
2.1 Single-collection and Multi-collection Packages
2.2 Package Sources
2.3 Package Catalogs
2.4 Explicit vs. Auto-Installation
2.5 Package Conflicts
2.6 Package Updates
2.7 Package Scopes
3 Using raco pkg
3.1 raco pkg install
3.2 raco pkg update
3.3 raco pkg remove
3.4 raco pkg new
3.5 raco pkg show
3.6 raco pkg migrate
3.7 raco pkg create
3.8 raco pkg config
3.9 raco pkg catalog-show
3.10 raco pkg catalog-copy
3.11 raco pkg catalog-archive
3.12 raco pkg archive
3.13 raco pkg empty-trash
4 Package Metadata
5 Source, Binary, and Built Packages
6 Developing Packages with Git
6.1 Linking a Git Checkout as a Directory
6.2 Linking a Git Checkout as a Clone
6.3 Interactions Between git and raco pkg
7 Package APIs
7.1 Functions for raco pkg
7.2 Package Management Functions
7.3 Package Paths and Database
7.4 Package Source Parsing
7.5 Package Catalog Database
7.6 Package Directories Catalog
7.7 Package Management Environment Variables
8 Package Catalog Protocol
8.1 Remote and Directory Catalogs
8.2 SQLite Catalogs
9 PLaneT Compatibility
10 FAQ
11 Future Plans
11.1 Short Term
11.2 Long Term
12 How Package Installation and Distribution Works
12.1 Relative References
12.2 Separate Documentation Rendering
12.3 Cross-Document HTML References
12.4 HTML Documentation Searching and Start Page