Connect to the SSH daemon at URI, a URI object with the 'ssh' scheme.

Connect to the daemon at URI (a string), or, if PORT is not #f, use it as the I/O port over which to communicate to a build daemon.

When RESERVE-SPACE? is true, instruct it to reserve a little bit of extra space on the file system so that the garbage collector can still operate, should the disk become full. When CPU-AFFINITY is true, it must be an integer corresponding to an OS-level CPU number to which the daemon's worker process for this connection will be pinned. If NON-BLOCKING?, use a non-blocking socket when using the file, unix or guix URI schemes. If BUILT-IN-BUILDERS is provided, it should be a list of strings and this will be used instead of the builtin builders provided by the build daemon. Return a server object.

Remove the permanent garbage collector root pointing to TARGET. Raise an error if there is no such root.

Like 'mapm' in %STORE-MONAD, but accumulate 'build-things' calls and coalesce them into a single call.

Set STORE's CACHE to VALUE.

This is a mutating version that should be avoided. Prefer the functional 'set-store-connection-cache' instead, together with using %STORE-MONAD.

Make PATH a temporary root for the duration of the current session. Return #t.

Apply PROC over each element of LST, accumulating 'build-things' calls and coalescing them into a single call.

CUTOFF is the threshold above which we stop accumulating unresolved nodes.

Convert MAPPING, an alist like:

(("guix/build/utils.scm" . "…/utils.scm"))

to a tree suitable for 'add-file-tree-to-store' and 'interned-file-tree'.

Like 'references', but cache results.

Allocate a new cache for store connections and return its identifier. Said identifier can be passed as an argument to

Return the cache of STORE identified by CACHE, an identifier as returned by 'allocate-store-connection-cache'.

Return #t if binary substitutes are available for PATH, and #f otherwise.

Make the symlink FILE-NAME an indirect root for the garbage collector: whatever store item FILE-NAME points to will not be collected. Return #t on success.

FILE-NAME can be anywhere on the file system, but it must be an absolute file name--it is the caller's responsibility to ensure that it is an absolute file name.

Add the contents of FILE-NAME under BASENAME to the store. When RECURSIVE? is false, FILE-NAME must designate a regular file--not a directory nor a symlink. When RECURSIVE? is true and FILE-NAME designates a directory, the contents of FILE-NAME are added recursively; if FILE-NAME designates a flat file and RECURSIVE? is true, its contents are added, and its permission bits are kept. HASH-ALGO must be a string such as "sha256".

When RECURSIVE? is true, call (SELECT? FILE STAT) for each directory entry, where FILE is the entry's absolute file name and STAT is the result of 'lstat'; exclude entries for which SELECT? does not return true.

Verify the integrity of the store and return false if errors remain, and true otherwise. When REPAIR? is true, repair any missing or altered store items by substituting them (this typically requires root privileges because it is not an atomic operation.) When CHECK-CONTENTS? is true, check the contents of store items; this can take a lot of time.