Change:
Many more commands wrap `writeTextFile` including `writeText`, `writeTextDir`, `writeScript`, and `writeScriptBin`. These are convenience functions over `writeTextFile`. <ins> Here are a few examples: ```nix # Writes my-file to /nix/store/<store path> writeTextFile { name = "my-file"; text = '' Contents of File ''; } # See also the `writeText` helper function below. # Writes executable my-file to /nix/store/<store path>/bin/my-file writeTextFile { name = "my-file"; text = '' Contents of File ''; executable = true; destination = "/bin/my-file"; } # Writes contents of file to /nix/store/<store path> writeText "my-file" '' Contents of File ''; # Writes contents of file to /nix/store/<store path>/share/my-file writeTextDir "share/my-file" '' Contents of File ''; # Writes my-file to /nix/store/<store path> and makes executable writeScript "my-file" '' Contents of File ''; # Writes my-file to /nix/store/<store path>/bin/my-file and makes executable. writeScriptBin "my-file" '' Contents of File ''; # Writes my-file to /nix/store/<store path> and makes executable. writeShellScript "my-file" '' Contents of File ''; # Writes my-file to /nix/store/<store path>/bin/my-file and makes executable. writeShellScriptBin "my-file" '' Contents of File ''; ``` ## `concatTextFile`, `concatText`, `concatScript` {#trivial-builder-concatText} These functions concatenate `files` to the Nix store in a single file. This is useful for configuration files structured in lines of text. `concatTextFile` takes an attribute set and expects two arguments, `name` and `files`. `name` corresponds to the name used in the Nix store path. `files` will be the files to be concatenated. You can also set `executable` to true to make this file have the executable bit set. `concatText` and`concatScript` are simple wrappers over `concatTextFile`. Here are a few examples: ```nix # Writes my-file to /nix/store/<store path> concatTextFile { name = "my-file"; files = [ drv1 "${drv2}/path/to/file" ]; } # See also the `concatText` helper function below. # Writes executable my-file to /nix/store/<store path>/bin/my-file concatTextFile { name = "my-file"; files = [ drv1 "${drv2}/path/to/file" ]; executable = true; destination = "/bin/my-file"; } # Writes contents of files to /nix/store/<store path> concatText "my-file" [ file1 file2 ] # Writes contents of files to /nix/store/<store path> concatScript "my-file" [ file1 file2 ] ``` </ins> ## `writeShellApplication` {#trivial-builder-writeShellApplication} This can be used to easily produce a shell script that has some dependencies (`runtimeInputs`). It automatically sets the `PATH` of the script to contain all of the listed inputs, sets some sanity shellopts (`errexit`, `nounset`, `pipefail`), and checks the resulting script with [`shellcheck`](https://github.com/koalaman/shellcheck).

Discussion:
In my config I have and when building it gives me the following error: However if I replace it with it builds without errors. Even weirder, If I do it works without problems. The configuration builds normally system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:
Tried surrounding the path in quotes?
wouldn't that make a string and not include the file in the store? As it stands, the files does get included in the store because succeds without problems.