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

Return the list of live store paths---i.e., store paths still referenced, and thus not subject to being garbage-collected.

Return the base path of a path in the store.

Add the given TREE to the store on SERVER. TREE must be an entry such as:

("my-tree" directory ("a" regular (data "hello")) ("b" symlink "a") ("c" directory ("d" executable (file "/bin/sh"))))

This is a generalized version of 'add-to-store'. It allows you to reproduce an arbitrary directory layout in the store without creating a derivation.

Return #t if PATH is a store path.

This is a lightweight check. Use 'valid-path-syntax?' to validate untrusted input.

Return the package name part of PATH, a file name in the store.

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.

Add a garbage collector root pointing to TARGET, an element of the store, preventing TARGET from even being collected. This can also be used if TARGET does not exist yet.

Raise an error if the caller does not have write access to the GC root directory.

Monadic version of 'query-path-info' that returns #f when ITEM is not in the store.

Return a copy of STORE where CACHE has the given VALUE. CACHE must be a value returned by 'allocate-store-connection-cache'.

Return true if PATH is syntactically a valid store path. Unlike 'store-path?', this can be used to validate untrusted input.

This must not be confused with 'valid-path?'.

Remove ITEMS from the list of cached build failures and return #t.

This makes sense only when the daemon was started with '--cache-failures'.