Build the given Mix package, applying all of PHASES in order.

Rewrite 'package.json' to allow the build to proceed without packages listed in 'dependencies-to-remove', a list of strings naming npm packages.

To prevent the deleted dependencies from being reintroduced, use this function only after the 'patch-dependencies' phase.

Provides a lambda to supply to modify-json which deletes the specified `fields` which is a list of field-paths as mentioned in `modify-json-fields`. Examples: (delete-fields '( ("path" "to" "field") "path.to.other.field"))

Provides a lambda to supply to modify-json which replaces the value of the supplied field. `fields` is a list of pairs, where the first element is the field-path and the second element is the value to replace the target with. Examples: (replace-fields '( (("path" "to" "field") "new field value") ("path.to.other.field" "new field value")))

Provides a lambda to supply to modify-json which modifies the specified json file. - `fields` is a list procedure-specific data structures which should include the definition of a `field-path` in one of two syntaxes: dot-syntax string such as `"devDependencies.esbuild"`, or a list of strings such as `(list "devDependencies" "esbuild")`. - `field-modifier` is a lambda which is invoked at the position of the field. It is supplied with the current field definition, the association list (alist) at the field location in the json file, and the field name, also called `key`. - `field-path-mapper` is a lambda which instructs where the field-path is located within the field structure. - `insert?` allows the creation of the field and any missing intermediate fields. - `strict?` causes an error to be thrown if the exact field-path is not found in the data

Like 'with-atomic-file-replacement', but PROC is called with a single argument---the result of parsing FILE's contents as json---and should a value to be written as json to the replacement FILE.

Provide package.json modifying callbacks such as (delete-dependencies ...)

Build the given package, applying all of PHASES in order.

Create a self-contained tarball TARBALL-FILE-NAME from PROFILE, optionally compressing it with COMPRESSOR-COMMAND, the complete command-line string to use for the compressor.

Populate the root profile directory with SYMLINKS and a Guix database, when LOCALSTATEDIR? is set, and a pre-computed STORE-DATABASE is provided. The directory is created as "root" in the current working directory. When DEDUPLICATE? is true, deduplicate the store items, which relies on hard links. It needs to run in an environment where

Return the base GNU tar options required to produce deterministic archives deterministically. When TAR, a GNU tar command file name, is provided, the `--sort' option is used only if supported. When COMPRESSOR, a command such as '("gzip" "-9n"), is provided, the compressor is explicitly specified via the `-I' option.

Build the given Perl package, applying all of PHASES in order.

Translate the cross-references that appear in texi, the initial translation of a Texinfo file, using the msgid/msgstr pairs from pofile.

Read a .po file from PORT and return an alist of msgid and msgstr.

Ensure DIRECTORY exists and is writable. If DIRECTORY is currently a symlink (to a read-only directory in the store), then delete the symlink and instead make DIRECTORY a "real" directory containing symlinks.

Assuming both OLD and NEW are absolute file names, make NEW a symlink to OLD, but using a relative file name.

Build a user profile from MANIFEST, an sexp, and EXTRA-INPUTS, a list of store items, in directory OUTPUT, using SYMLINK to create symlinks. Create OUTPUT/etc/profile with Bash definitions for all the variables listed in the search paths of MANIFEST's entries.

Prepend the site-package of OUTPUT to GUIX_PYTHONPATH. This is useful when running checks after installing the package.