Return the list of path that refer to PATH.

Lift PROC, a procedure whose first argument is a connection to the store, in the store monad.

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.

Return an output path for OUTPUT (the name of the output as a string) of the derivation called NAME with hash HASH.

Collect garbage from the store at SERVER. If MIN-FREED is non-zero, then collect at least MIN-FREED bytes. Return the paths that were collected, and the number of bytes freed.

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

Return as a monadic value the absolute file name in the store of the file containing DATA, a bytevector. REFERENCES is a list of store items that the resulting text file refers to; it defaults to the empty list.

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

Return the list of dead store paths---i.e., store paths no longer referenced, and thus subject to being garbage-collected.

Return #t if PATH is a store path.

Return the direct store path part of PATH, stripping components after '/gnu/store/xxxx-foo'.

Add BYTES under file NAME in the store, and return its store path. REFERENCES is the list of store paths referred to by the resulting store path.

Return information about the subset of PATHS that is substitutable. For each substitutable path, a `substitutable?' object is returned; thus, the resulting list can be shorter than PATHS. Furthermore, that there is no guarantee that the order of the resulting list matches the order of PATHS.

Export the store paths listed in PATHS to PORT, in topological order, signing them if SIGN? is true. When RECURSIVE? is true, export the closure of PATHS---i.e., PATHS and all their dependencies.

START, PROGRESS, and FINISH are used to track progress of the data transfer. START is a one-argument that is passed the list of store items that will be transferred; it returns values that are then used as the initial state threaded through PROGRESS calls. PROGRESS is passed the store item about to be sent, along with the values previously return by START or by PROGRESS itself. FINISH is called when the last store item has been called.

Return the build log file for FILE, or #f if none could be found. FILE must be an absolute store file name, or a derivation file name.