7.7 Package Management Environment Variables

► |  | Package Management in Racket

1 | Getting Started with Packages
2 | Package Concepts
3 | Using raco pkg
4 | Package Metadata
5 | Source, Binary, and Built Packages
6 | Developing Packages with Git
7 | Package APIs
8 | Package Catalog Protocol
9 | PLane T Compatibility
10 | FAQ
11 | Future Plans
12 | How Package Installation and Distribution Works

▼ | 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

9.1
Racket
top contents ← prev up next →

### 7.7 Package Management Environment Variables🔗ℹ

If the PLT_PKG_SSL_NO_VERIFY environment variable is set, server certificates are not validated for HTTPS connections. When accessing Git servers over HTTPS, GIT_SSL_NO_VERIFY must be set, too, to disable certificate validation.

As noted in the specification of GitHub-repository package sources, if the PLT_USE_GITHUB_API environment variable is set, GitHub packages are obtained using the GitHub API protocol instead of using the Git protocol.

top contents ← prev up next →