7.3 Package Paths and Database
utilities for working with package paths and installed-package
A structure type that is used to report installed-package information.
The orig-pkg field describes the source of the package as
installed, where 'catalog refers to a package that was
installed by consulting a catalog with a package name, and so on. The
two-element 'catalog form records a URL for a Git or GitHub
package source when the catalog reported such a source, and the URL is
used for operations that adjust 'clone-form installations.
Changed in version 126.96.36.199 of package base: Added 'clone and two-level
'catalog variants for
A structure subtype that represents a package that is installed as
Structure subtypes that are used when the installation directory for a
package does not match the package name, but is instead
dir-name. The directory name always includes a +
(which is disallowed in a package name).
Returns the installed package containing path, if any.
If cache is not #f, then it is consulted and
modified to cache installed-package information across calls to
path->pkg (with the assumption that the set of installed
packages does not change across calls that receive the same
, but returns a second value that represents
the remainder of path
within the package’s directory.
, but returns a third value for the package’s
, but returns a third value for a
collection name if the package is a single-collection package,
Like path->pkg+subpath+collects, but returns a fourth value for
the package’s installation scope.
Returns the path of the directory that holds installed packages in the
given scope. The user-version argument is used to generate
the result for 'user scope.
Returns a hash table representing the currently installed packages
in the specified scope.
Reads a hash table from path, logging any errors and
returning an empty hash table if path does not exist or if an
error is encountered.