5 Utility Libraries

▼ |  | PLane T: Automatic Package Distribution

1 | Using PLane T
2 | The PLane T Search Order
3 | The raco planet Command-Line Tool
4 | The planet Language
5 | Utility Libraries
6 | Developing Packages for PLane T

► | 5 | Utility Libraries

5.1 | Resolver
5.2 | Client Configuration
5.3 | Package Archives
5.4 | Package Utils
5.5 | Package Version
5.6 | Macros and Syntax Objects
5.7 | Scribble Documentation
5.8 | Terse Status Updates
5.9 | The Cache File’s Path

On this page:

5.1 Resolver
planet-module-name-resolver
get-planet-module-path/ pkg
resolve-planet-path
download?
install?
5.1.1 Resolver file locking
5.2 Client Configuration
PLANET-BASE-DIR
PLANET-DIR
CACHE-DIR
UNINSTALLED-PACKAGE-CACHE
LINKAGE-FILE
LOG-FILE
USE-HTTP-DOWNLOADS?
HTTP-DOWNLOAD-SERVLET-URL
PLANET-SERVER-NAME
PLANET-SERVER-PORT
HARD-LINK-FILE
PLANET-ARCHIVE-FILTER
PLANET-CODE-VERSION
DEFAULT-PACKAGE-LANGUAGE
5.3 Package Archives
get-all-planet-packages
get-installed-planet-archives
get-hard-linked-packages
5.4 Package Utils
download/ install-pkg
install-pkg
get-package-spec
pkg-spec?
current-cache-contents
current-linkage
make-planet-archive
build-scribble-docs?
force-package-building?
download-package
pkg->download-url
get-package-from-cache
lookup-package-by-keys
unpack-planet-archive
remove-pkg
erase-pkg
display-plt-file-structure
display-plt-archived-file
unlink-all
add-hard-link
remove-hard-link
resolve-planet-path
path->package-version
exn: fail: planet
pkg?
5.5 Package Version
this-package-version
this-package-version-symbol
this-package-version-name
this-package-version-owner
this-package-version-maj
this-package-version-min
this-package-in
make-planet-symbol
package-version->symbol
5.6 Macros and Syntax Objects
syntax-source-planet-package
syntax-source-planet-package-owner
syntax-source-planet-package-name
syntax-source-planet-package-major
syntax-source-planet-package-minor
syntax-source-planet-package-symbol
make-planet-require-spec
5.7 Scribble Documentation
this-package-in
racketmod/ this-package
racketmodname/ this-package
racketmodlink/ this-package
defmodule/ this-package
defmodulelang/ this-package
defmodulereader/ this-package
defmodule*/ this-package
defmodulelang*/ this-package
defmodulereader*/ this-package
defmodule*/ no-declare/ this-package
defmodulelang*/ no-declare/ this-package
defmodulereader*/ no-declare/ this-package
declare-exporting/ this-package
5.8 Terse Status Updates
planet-terse-register
planet-terse-log
planet-terse-set-key
5.9 The Cache File’s Path
get-planet-cache-path

9.3
Racket
top contents ← prev up next →

## 5 Utility Libraries🔗ℹ

The planet collection provides configuration and utilities for using PLaneT.

### 5.1 Resolver🔗ℹ

(require planet/resolver) | package: base

The primary purpose of this library to for require to find PLaneT packages. It also, however, provides some utilities for manipulating the resolvers behavior.

> procedure (planet-module-name-resolver r-m-p) → void?
> r-m-p : resolved-module-path?
> (planet-module-name-resolver |  | spec |
> |  | module-path |
> |  | stx |
> |  | load |
> |  | orig-paramz) |
> → resolved-module-path?
> spec : (or/c module-path? path?)
> module-path : (or/c #f resolved-module-path?)
> stx : (or/c #f syntax?)
> load : boolean?
> orig-paramz : parameterization?

This implements the PLaneT module resolution process. It is dynamic-required by racket when the first PLaneT module require is needed. It acts much like a current-module-name-resolver would, but racket provides it with a special parameterization? (giving it special privileges) that it uses when installing new packages.

> > procedure
> > (get-planet-module-path/pkg |  | spec |  |  |  |
> > |  | module-path |  |  |  |
> > |  | stx) |  | → |  |
> > path? |  | pkg?
> spec : (or/c module-path? path?)
> module-path : (or/c #f resolved-module-path?)
> stx : (or/c #f syntax?)

Returns the path corresponding to the package (interpreting the arguments the same way as planet-module-name-resolver and (current-module-name-resolver)).

> procedure (resolve-planet-path planet-path) → path?
> planet-path : any/c

Returns the file system path to the file specified by the given quoted PLaneT require specification. This function downloads and installs the specified package if necessary, but does not verify that the actual file within it actually exists.

If the PLaneT package is not actually installed, then this function expects to be called with a very powerful security guard, one that is available to the built-in module name resolver, but not generally available to user code. So probably this function will fail (possibly deadlock).

This is the same function as the one with the same name, exported by planet/util.

> parameter (download?) → boolean?
> (download? dl?) → void?
> dl? : boolean?

A parameter that controls if PLaneT attempts to download a package that isn’t already present. If the package isn’t present, the resolver will raise the exn:fail:planet? exception instead of downloading it.

> parameter (install?) → boolean?
> (install? inst?) → void?
> inst? : boolean?

A parameter that controls if PLaneT attempts to install a package that isn’t already installed. If the package isn’t installed, the resolver will raise the exn:fail:planet? exception instead of installing it.

#### 5.1.1 Resolver file locking🔗ℹ

When PLaneT is asked to resolve a module path for loading the file (e.g., when the last argument to the (current-module-name-resolver) is #t and that resolver triggers a call to the PLaneT resolver), it finds the directory where the files are installed, say in this directory, which corresponds to version 1.2 of dyoo’s closure-compile.plt package:

> "(CACHE-DIR)/dyoo/closure-compile.plt/1/2/"

If the file

> "(CACHE-DIR)/dyoo/closure-compile.plt/1/2.SUCCESS"

is there, it assumes that there is no installation needed and it just continues, using the path to the file inside that directory.

If the "2.SUCCESS" file is not there, then it attempts to grab an 'exclusive filesystem lock on this file (via port-try-file-lock?)

> "(CACHE-DIR)/dyoo/closure-compile.plt/1/2.LOCK"

If it gets the lock, it then proceeds with the installation, calling raco setup to do the unpacking, compilation, and docs building. After the unpacking has finished, but before beginning compilation and docs building, it creates the "2.UNPACKED" file:

> "(CACHE-DIR)/dyoo/closure-compile.plt/1/2.UNPACKED"

When compilation and docs build are complete, it creates the "2.SUCCESS" file:

> "(CACHE-DIR)/dyoo/closure-compile.plt/1/2.SUCCESS"

and releases the lock on the "2.LOCK" file.

If it fails to get the lock on "2.LOCK" and it does not already hold the lock (due to a re-entrant call to the resolver (the resolver knows about locks it holds via an internal parameter that gets created when the planet/resolver module is instantiated) then it goes into a loop that polls for the existence of the "2.SUCCESS" file; when it that file appears, it just continues, without installing anything (since that means someone else installed it).

In some situations (e.g., when a new namespace is created and a fresh instantiation of planet/resolver is created), PLaneT can be fooled into thinking that it does not hold the lock on some installation. In order to cope with these situations somewhat, PLaneT takes an easier path when the resolver is only looking for information about package files (i.e., when the last argument to the resolver is #f, or when get-planet-module-path/pkg is called directly (as opposed to being called via module resolution). In those cases, PLaneT will look only for the "2.UNPACKED" file instead of the "2.SUCCESS" file.

### 5.2 Client Configuration🔗ℹ

(require planet/config) | package: base

The planet/config library provides several parameters useful for configuring how PLaneT works.

Note that while these parameters can be useful to modify programmatically, PLaneT code runs at module-expansion time, so most user programs cannot set them until PLaneT has already run. Therefore, to meaningfully change these settings, it is best to manually edit the "config.rkt" file.

> parameter (PLANET-BASE-DIR) → path-string?
> (PLANET-BASE-DIR dir) → void?
> dir : path-string?

The root of the tree where planet stores all of its files. Defaults to

> (let ([plt-planet-dir-env-var (getenv "PLTPLANETDIR")])
> (if plt-planet-dir-env-var
> (string->path plt-planet-dir-env-var)
> (build-path (find-system-path 'addon-dir)
> "planet"
> (PLANET-CODE-VERSION))))

> parameter (PLANET-DIR) → path-string?
> (PLANET-DIR dir) → void?
> dir : path-string?

The root of the version-specific PLaneT files. Defaults to (build-path (PLANET-BASE-DIR) (get-installation-name)).

> parameter (CACHE-DIR) → path-string?
> (CACHE-DIR dir) → void?
> dir : path-string?

The root of the PLaneT client’s cache directory.

> parameter (UNINSTALLED-PACKAGE-CACHE) → path-string?
> (UNINSTALLED-PACKAGE-CACHE dir) → void?
> dir : path-string?

The root of the PLaneT client’s uninstalled-packages cache. PLaneT stores package distribution files in this directory, and searches for them in this directory for them if necessary. Unlike the main PLaneT cache, which contains compiled files and is specific to each particular version of Racket, the uninstalled package cache is shared by all versions of Racket that use the same package repository, and it is searched if a package is not installed in the primary cache and cannot be downloaded from the central PLaneT repository (for instance due to a loss of Internet connectivity). This behavior is intended to primarily benefit users who upgrade their Racket installations frequently.

> parameter (LINKAGE-FILE) → path-string?
> (LINKAGE-FILE file) → void?
> file : path-string?

The file to use as the first place PLaneT looks to determine how a particular PLaneT dependence in a file should be satisfied. The contents of this file are used to ensure that no "magic upgrades" occur after a package is installed. The default is the file "LINKAGE" in the root PLaneT directory.

> parameter (LOG-FILE) → (or/c path-string? false?)
> (LOG-FILE file) → void?
> file : (or/c path-string? false?)

If #f, indicates that no logging should take place. Otherwise specifies the file into which logging should be written. The default is the file "INSTALL-LOG" in the root PLaneT directory.

> parameter (USE-HTTP-DOWNLOADS?) → boolean?
> (USE-HTTP-DOWNLOADS? bool) → void?
> bool : any/c

PLaneT can use two different protocols to retrieve packages. If #t, PLaneT will use the HTTP protocol; if #f it will use the custom-built PLaneT protocol. The default value for this parameter is #t and setting this parameter to #f is not recommended.

> parameter (HTTP-DOWNLOAD-SERVLET-URL) → string?
> (HTTP-DOWNLOAD-SERVLET-URL url) → void?
> url : string?

The URL for the servlet that will provide PLaneT packages if USE-HTTP-DOWNLOADS? is #t, represented as a string. This defaults to the value of the PLTPLANETURL environment variable if it is set and otherwise is "http://planet.racket-lang.org/servlets/planet-servlet.rkt".

> parameter (PLANET-SERVER-NAME) → string?
> (PLANET-SERVER-NAME host) → void?
> host : string?

The name of the PLaneT server to which the client should connect if USE-HTTP-DOWNLOADS? is #f. The default value for this parameter is "planet.racket-lang.org".

> parameter (PLANET-SERVER-PORT) → natural-number?
> (PLANET-SERVER-PORT port) → void?
> port : natural-number?

The port on the server the client should connect to if USE-HTTP-DOWNLOADS? is #f. The default value for this parameter is 270.

> parameter (HARD-LINK-FILE) → path?
> (HARD-LINK-FILE file) → void?
> file : path?

The name of the file where hard links are saved. Defaults to (build-path (PLANET-BASE-DIR) (get-installation-name) "HARD-LINKS").

> parameter (PLANET-ARCHIVE-FILTER) → (or/c #f string? regexp?)
> (PLANET-ARCHIVE-FILTER regexp-filter) → void?
> regexp-filter : (or/c #f string? regexp?)

A regular-expression based filter that is used to skip files when building a PLaneT archive.

> parameter (PLANET-CODE-VERSION) → string?
> (PLANET-CODE-VERSION vers) → void?
> vers : string?

Used to compute PLANET-BASE-VERSION.

> parameter (DEFAULT-PACKAGE-LANGUAGE) → string?
> (DEFAULT-PACKAGE-LANGUAGE vers) → void?
> vers : string?

The package language used when communicating with the server to find which package to download.

Defaults to (version).

### 5.3 Package Archives🔗ℹ

(require planet/planet-archives) | package: base

> procedure (get-all-planet-packages)
> | → |  |
> (listof (list/c (and/c path? absolute-path?) string? string? (listof string?)
> exact-nonnegative-integer?
> exact-nonnegative-integer?))

Returns the installed planet package. Each element of the result list corresponds to a single package. The first element in an inner list is the location of the installed files. The second and third elements are the owner and package names. The last two elements are the major and minor verisons

> procedure (get-installed-planet-archives)
> | → |  |
> (listof (list/c (and/c path? absolute-path?) string? string? (listof string?)
> exact-nonnegative-integer?
> exact-nonnegative-integer?))

Like get-all-planet-archives, except that it does not return packages linked in with “raco planet link”.

> procedure (get-hard-linked-packages)
> | → |  |
> (listof (list/c (and/c path? absolute-path?) string? string? (listof string?)
> exact-nonnegative-integer?
> exact-nonnegative-integer?))

Like get-all-planet-archives, except that it return only packages linked in with “raco planet link”.

### 5.4 Package Utils🔗ℹ

(require planet/util) | package: planet-lib

The planet/util library supports examination of the pieces of PLaneT. It is meant primarily to support debugging and to allow easier development of higher-level package-management tools. The functionality exposed by the raco planet command-line tool is also available programmatically through this library.

> procedure (download/install-pkg owner pkg maj min) → (or/c pkg? #f)
> owner : string?
> pkg : (and/c string? #rx"[.]plt$")
> maj : natural-number/c
> min : natural-number/c

Downloads and installs the package specifed by the given owner name, package name, major and minor version number. Returns false if no such package is available; otherwise returns a package structure for the installed package.

The pkg argument must end with ".plt".

> procedure (install-pkg pkg-spec file maj min) → (or/c pkg-spec? #f)
> pkg-spec : pkg-spec?
> file : path-string?
> maj : natural-number/c
> min : natural-number/c

Installs the package represented by the arguments, using the pkg-spec argument to find the path and name of the package to install.

See get-package-spec to build a pkg-spec argument.

Returns a new pkg-spec? corresponding to the package that was actually installed.

> procedure (get-package-spec owner pkg [maj min]) → pkg-spec?
> owner : string?
> pkg : (and/c string? #rx"[.]plt$")
> maj : (or/c #f natural-number/c) = #f
> min : (or/c #f natural-number/c) = #f

Builds a pkg-spec? corresponding to the package specified by owner, pkg, maj, and min.

The pkg argument must end with the string ".plt".

> procedure (pkg-spec? v) → boolean?
> v : any/c

Recognizes the result of get-package-spec (and install-pkg).

> parameter (current-cache-contents)
> | → |  |
> (listof
> (list/c string?
> (listof
> (list/c string?
> (cons/c natural-number/c
> (listof natural-number/c))))))
> (current-cache-contents contents) → void?
> | contents |  | : |  |
> (listof
> (list/c string?
> (listof
> (list/c string?
> (cons/c natural-number/c
> (listof natural-number/c))))))

Holds a listing of all package names and versions installed in the local cache.

> procedure (current-linkage)
> | → |  |
> (listof (list/c path-string?
> (list/c string?
> (list/c string?)
> natural-number/c
> natural-number/c)))

Returns the current linkage table.

The linkage table is an association between file locations (encoded as path strings) and concrete planet package versions. If a require line in the associated file requests a package, this table is consulted to determine a particular concrete package to satisfy the request.

> procedure (make-planet-archive directory [output-file]) → path-string?
> directory : path-string?
> | output-file |  | : |  | (or/c path? path-string?)
> |  |  | = |  | (string-append (path->string name) ".plt")

Makes a .plt archive file suitable for PLaneT whose contents are all files in the given directory and returns that file’s name. If the optional filename argument is provided, that filename will be used as the output file’s name.

See also build-scribble-docs? and force-package-building?

> parameter (build-scribble-docs?) → boolean?
> (build-scribble-docs? b) → void?
> b : boolean?

Determines if make-planet-archive builds scribble docs (or not).

> parameter (force-package-building?) → boolean?
> (force-package-building? b) → void?
> b : boolean?

Determines if make-planet-archive signals an error and refuses to continue packaging for certain, more significant errors.

Defaults to #t, and thus packaging will signal errors.

> procedure (download-package pkg-spec)
> | → |  |
> (or/c (list/c #true path? natural-number/c natural-number/c)
> string?
> (list/c #false string?))
> pkg-spec : pkg-spec?

Downloads the package given by pkg-spec. If the result is a list whose first element is #true, then the package was downloaded successfully and the rest of the elements of the list indicate where it was downloaded, and the precise version number.

The other two possible results indicate errors. If the result is a list, then the server is saying that there is no matching package; otherwise the error is some lower-level problem (perhaps no networking, etc.)

> procedure (pkg->download-url pkg) → url?
> pkg : pkg?

Returns the url for a given package.

> procedure (get-package-from-cache pkg-spec) → (or/c #false path?)
> pkg-spec : pkg-spec?

Returns the location of the already downloaded package, if it exists (and #false otherwise).

> > procedure
> > (lookup-package-by-keys |  | owner |
> > |  | name |
> > |  | major |
> > |  | minor-lo |
> > |  | minor-hi) |
> | → |  |
> (or/c (list/c path?
> string?
> string?
> (listof string?)
> exact-nonnegative-integer?
> exact-nonnegative-integer?)
> #false)
> owner : string?
> name : string?
> major : exact-nonnegative-integer?
> minor-lo : exact-nonnegative-integer?
> minor-hi : exact-nonnegative-integer?

Looks up and returns a list representation of the package named by the given owner, package name, major and (range of) minor version(s).

> procedure (unpack-planet-archive plt-file output-dir) → any
> plt-file : (or/c path? path-string?)
> output-dir : (or/c path? path-string?)

Unpacks the PLaneT archive with the given filename, placing its contents into the given directory (creating that path if necessary).

> procedure (remove-pkg owner pkg maj min) → any
> owner : string?
> pkg : (and/c string? #rx"[.]plt$")
> maj : natural-number/c
> min : natural-number/c

Removes the specified package from the local planet cache, deleting the installed files.

> procedure (erase-pkg owner pkg maj min) → any
> owner : string?
> pkg : (and/c string? #rx"[.]plt$")
> maj : natural-number/c
> min : natural-number/c

Like remove-pkg, removes the specified package from the local planet cache and deletes all of the files corresponding to the package, but also deletes the cached ".plt" file (so it will be redownloaded later).

> procedure (display-plt-file-structure plt-file) → any
> plt-file : (or/c path-string? path?)

Print a tree representing the file and directory structure of the PLaneT archive .plt file named by plt-file to (current-output-port).

> > procedure
> > (display-plt-archived-file |  | plt-file |  |  |  |
> > |  | file-to-print) |  | → |  | any
> plt-file : (or/c path-string? path?)
> file-to-print : string?

Print the contents of the file named file-to-print within the PLaneT archive .plt file named by plt-file to (current-output-port).

> procedure (unlink-all) → any

Removes the entire linkage table from the system, which will force all modules to relink themselves to PLaneT modules the next time they run.

> procedure (add-hard-link owner pkg maj min dir) → any
> owner : string?
> pkg : (and/c string? #rx"[.]plt$")
> maj : natural-number/c
> min : natural-number/c
> dir : path?

Adds a development link between the specified package and the given directory; once a link is established, PLaneT will treat the cache as having a package with the given owner, name, and version whose files are located in the given path. This is intended for package development; users only interested in using PLaneT packages available online should not need to create any development links.

If the specified package already has a development link, this function first removes the old link and then adds the new one.

The pkg argument must end with the string ".plt".

> > procedure
> > (remove-hard-link |  | owner |  |  |  |
> > |  | pkg |  |  |  |
> > |  | maj |  |  |  |
> > |  | min |  |  |  |
> > | [ | #:quiet? quiet?]) |  | → |  | any
> owner : string?
> pkg : (and/c string? #rx"[.]plt$")
> maj : natural-number/c
> min : natural-number/c
> quiet? : boolean? = #false

Removes any hard link that may be associated with the given package.

The pkg argument must end with the string ".plt". The maj and min arguments must be integers. This procedure signals an error if no such link exists, unless #:quiet? is #true.

> procedure (resolve-planet-path spec) → path?
> spec : quoted-planet-require-spec?

This is the same function as the one with the same name, exported by planet/resolver.

> procedure (path->package-version p)
> → (or/c (list/c string? string? natural-number/c natural-number/c) #f)
> p : path?

Given a path that corresponds to a PLaneT package (or some part of one), produces a list corresponding to its name and version, exactly like (this-package-version). Given any other path, produces #f.

> > struct
> > (struct |  | exn:fail:planet exn:fail (message continuation-marks)
> #:extra-constructor-name make-exn:fail:planet)
> message : string?
> continuation-marks : continuation-mark-set?

This exception record is used to report planet-specific exceptions.

> procedure (pkg? v) → boolean?
> v : any/c

Determines if its argument is a pkg, the representation of an installed package.

### 5.5 Package Version🔗ℹ

Provides bindings for PLaneT developers that automatically produce references to the name and version of the containing PLaneT package so the same code may be reused across releases without accidentally referring to a different version of the same package.

(require planet/version) | package: planet-lib

> syntax (this-package-version)
> syntax (this-package-version-symbol)
> (this-package-version-symbol suffix-id)
> syntax (this-package-version-name)
> syntax (this-package-version-owner)
> syntax (this-package-version-maj)
> syntax (this-package-version-min)

Macros that expand into expressions that evaluate to information about the name, owner, and version number of the package in which they appear. this-package-version returns a list consisting of a string naming the package’s owner, a string naming the package, a number indicating the package major version and a number indicating the package minor version, or #f if the expression appears outside the context of a package. The macros this-package-version-name, this-package-version-owner, this-package-version-maj, and this-package-version-min produce the relevant fields of the package version list.

this-package-version-symbol produces a symbol suitable for use in planet module paths. For instance, in version 1:0 of the package package.plt owned by author, (this-package-version-symbol dir/file) produces 'author/package:1:0/dir/file. In the same package, (this-package-version-symbol) produces 'author/package:1:0.

> syntax (this-package-in suffix-id ...)

A require sub-form that requires modules from within the same PLaneT package version as the require, as referred to by each suffix-id. For instance, in version 1:0 of the package package.plt owned by author, (require (this-package-in dir/file)) is equivalent to (require (planet author/package:1:0/dir/file)).

Note: Use this-package-in when documenting PLaneT packages with Scribble to associate each documented binding with the appropriate package.

> procedure (make-planet-symbol stx [suffix]) → (or/c #false symbol?)
> stx : syntax?
> suffix : (or/c #false string?) = #false

Returns a symbol representing a require spec for the location of stx, as a planet package.

> procedure (package-version->symbol ver [suffix]) → (or/c #false symbol?)
> | ver |  | : |  |
> (or/c (list/c string? string? exact-nonnegative-integer? exact-nonnegative-integer?)
> #false)
> suffix : (or/c #false string?) = #false

Returns a symbol representing the require spec for ver, as a planet package.

### 5.6 Macros and Syntax Objects🔗ℹ

(require planet/syntax) | package: planet-lib

Provides bindings useful for PLaneT-based macros.

> procedure (syntax-source-planet-package stx) → (or/c list? #f)
> stx : syntax?
> procedure (syntax-source-planet-package-owner stx) → (or/c string? #f)
> stx : syntax?
> procedure (syntax-source-planet-package-name stx) → (or/c string? #f)
> stx : syntax?
> procedure (syntax-source-planet-package-major stx) → (or/c integer? #f)
> stx : syntax?
> procedure (syntax-source-planet-package-minor stx) → (or/c integer? #f)
> stx : syntax?
> > procedure
> > (syntax-source-planet-package-symbol |  | stx |
> > | [ | suffix]) |
> → (or/c symbol? #f)
> stx : syntax?
> suffix : (or/c symbol? #f) = #f

Produce output analogous to this-package-version, this-package-version-owner, this-package-version-name, this-package-version-maj, this-package-version-min, and this-package-version-symbol based on the source location of stx.

> procedure (make-planet-require-spec stx [suffix]) → syntax?
> stx : syntax?
> suffix : (or/c symbol? #f) = #f

Produces a require sub-form for the module referred to by suffix in the PLaneT package containing the source location of stx.

### 5.7 Scribble Documentation🔗ℹ

(require planet/scribble) | package: planet-doc

Provides bindings for documenting PLaneT packages.

> syntax (this-package-in suffix-id ...)

This binding from planet/version is also exported from planet/scribble, as it is useful for for-label imports in Scribble documentation.

> syntax (racketmod/this-package maybe-file suffix-id datum ...)
> syntax (racketmodname/this-package suffix-id)
> (racketmodname/this-package (unsyntax suffix-expr))
> syntax (racketmodlink/this-package suffix-id pre-content-expr ...)
> syntax (defmodule/this-package maybe-req suffix-id maybe-sources pre-flow ...)
> syntax (defmodulelang/this-package suffix-id maybe-sources pre-flow ...)
> (defmodulelang/this-package suffix-id
> #:module-paths (mod-suffix-id ...) maybe-sources
> pre-flow ...)
> syntax (defmodulereader/this-package suffix-id maybe-sources pre-flow ...)
> > syntax
> > (defmodule*/this-package maybe-req (suffix-id ...+)
> > maybe-sources pre-flow ...)
> > syntax
> > (defmodulelang*/this-package (suffix-id ...+)
> > maybe-sources pre-flow ...)
> (defmodulelang*/this-package (suffix-id ...+)
> #:module-paths (mod-suffix-id ...) maybe-sources
> pre-flow ...)
> > syntax
> > (defmodulereader*/this-package (suffix-id ...+)
> > maybe-sources pre-flow ...)
> > syntax
> > (defmodule*/no-declare/this-package maybe-req (suffix-id ...+)
> > maybe-sources pre-flow ...)
> > syntax
> > (defmodulelang*/no-declare/this-package (suffix-id ...+)
> > maybe-sources pre-flow ...)
> (defmodulelang*/no-declare/this-package (suffix-id ...+)
> #:module-paths (mod-suffix-id ...) maybe-sources pre-flow ...)
> > syntax
> > (defmodulereader*/no-declare/this-package (suffix-id ...+)
> > maybe-sources pre-flow ...)
> syntax (declare-exporting/this-package suffix-id ... maybe-sources)

Variants of racketmod, racketmodname, racketmodlink, defmodule, defmodulereader, defmodulelang, defmodule*, defmodulelang*, defmodulereader*, defmodule*/no-declare, defmodulelang*/no-declare, defmodulereader*/no-declare, and declare-exporting, respectively, that implicitly refer to the PLaneT package that contains the enclosing module.

The full module name passed to defmodule, etc is formed by appending the suffix-id or mod-suffix-id to the symbol returned by (this-package-version-symbol), separated by a / character, and tagging the resulting symbol as a planet module path. As a special case, if suffix-id is main, the suffix is omitted.

For example, within a package named package.plt by author, version 1:0, the following are equivalent:

> (defmodule/this-package dir/file)
> = (defmodule (planet author/package:1:0/dir/file))

and

> (defmodule/this-package main)
> = (defmodule (planet author/package:1:0))

### 5.8 Terse Status Updates🔗ℹ

(require planet/terse-info) | package: base

This module provides access to some PLaneT status information. This module is first loaded by PLaneT in the initial namespace (when PLaneT’s resolver is loaded), but PLaneT uses dynamic-require to load this module each time it wants to announce information. Similarly, the state of which procedures are registered (via planet-terse-register) is saved in the namespace, making the listening and information producing namespace-specific.

> procedure (planet-terse-register proc) → void?
> | proc |  | : |  |
> (-> (or/c 'download 'install 'docs-build 'finish)
> string?
> any/c)

Registers proc as a function to be called when planet-terse-log is called.

Note that proc is called asynchronously (ie, on some thread other than the one calling planet-terse-register).

> procedure (planet-terse-log id msg) → void?
> id : (or/c 'download 'install 'finish)
> msg : string?

This function is called by PLaneT to announce when things are happening. See also planet-terse-set-key.

> procedure (planet-terse-set-key key) → void?
> key : any/c

This sets a thread cell to the value of key. The value of the thread cell is used as an index into a table to determine which of the functions passed to planet-terse-register to call when planet-terse-log is called.

The table holding the key uses ephemerons and a weak hash table to ensure that when the key is unreachable, then the procedures passed to planet-terse-log cannot be reached through the table.

### 5.9 The Cache File’s Path🔗ℹ

(require planet/cachepath) | package: base

> procedure (get-planet-cache-path) → (and/c path? absolute-path?)

Returns the path to the "cache.rktd" file for the planet installation.
top contents ← prev up next →