view and edit package definitions

Print help about options shared between 'guix environment' and 'guix shell'.

Run the 'guix environment' command on OPTS, an alist resulting for command-line option processing with 'parse-command-line'.

spawn one-off software environments (deprecated)

Load the user-profile manifest (Scheme code) from FILE and return it.

Check if containers can be created and exit with an informative error message if any test fails.

Run COMMAND within a container that features the software in PROFILE. Environment variables are set according to the search paths of MANIFEST. The global shell is BASH, a file name for a GNU Bash binary in the store. When NETWORK?, access to the host system network is permitted. USER-MAPPINGS, a list of file system mappings, contains the user-specified host file systems to mount inside the container. If USER is not #f, each target of USER-MAPPINGS will be re-written relative to '/home/USER', and USER will be used for the passwd entry.

When EMULATE-FHS?, set up the container to follow the Filesystem Hierarchy Standard and provide a glibc that reads the cache from /etc/ld.so.cache. SETUP-HOOK is an additional setup procedure to be called, currently only used with the EMULATE-FHS? option.

When NESTING? is true, share all the store with the container and add Guix to its profile, allowing its use from within the container.

LINK-PROFILE? creates a symbolic link from ~/.guix-profile to the environment profile.

SYMLINKS must be a list of (SOURCE -> TARGET) tuples denoting symlinks to be added to the container.

Preserve environment variables whose name matches the one of the regexps in WHILE-LIST.

invoke the garbage collector

operate on Git repositories

view and query package dependency graphs