···

       
185
       
185
       
 
       
##### Comments

     

       
186
       
186
       
 
       
```

     

       
187
       
187
       
 
       


     

       
188
       
188
       
-
       
## Individual maintainer list {#reviewing-contributions-indvidual-maintainer-list}

     

       
188
       
188
       
+
       
## Individual maintainer list {#reviewing-contributions-individual-maintainer-list}

     

       
189
       
189
       
 
       


     

       
190
       
190
       
 
       
When adding users to `maintainers/maintainer-list.nix`, the following

     

       
191
       
191
       
 
       
checks should be performed:

     

···

       
1
       
1
       
-
       
# Generates the documentation for library functons via nixdoc. To add

     

       
1
       
1
       
+
       
# Generates the documentation for library functions via nixdoc. To add

     

       
2
       
2
       
 
       
# another library function file to this list, the include list in the

     

       
3
       
3
       
 
       
# file `doc/functions/library.xml` must also be updated.

     

       
4
       
4
       
 
       


     

···

       
93
       
93
       
 
       
- run `mix2nix > mix_deps.nix` in the upstream repo.

     

       
94
       
94
       
 
       
- pass `mixNixDeps = with pkgs; import ./mix_deps.nix { inherit lib beamPackages; };` as an argument to mixRelease.

     

       
95
       
95
       
 
       


     

       
96
       
96
       
-
       
If there are git depencencies.

     

       
96
       
96
       
+
       
If there are git dependencies.

     

       
97
       
97
       
 
       


     

       
98
       
98
       
 
       
- You'll need to fix the version artificially in mix.exs and regenerate the mix.lock with fixed version (on upstream). This will enable you to run `mix2nix > mix_deps.nix`.

     

       
99
       
99
       
 
       
- From the mix_deps.nix file, remove the dependencies that had git versions and pass them as an override to the import function.

     

···

       
8
       
8
       
 
       
* `customOCamlPackages` (optional, defaults to `null`, which lets Coq choose a version automatically), which can be set to any of the ocaml packages attribute of `ocaml-ng` (such as `ocaml-ng.ocamlPackages_4_10` which is the default for Coq 8.11 for example).

     

       
9
       
9
       
 
       
* `coq-version` (optional, defaults to the short version e.g. "8.10"), is a version number of the form "x.y" that indicates which Coq's version build behavior to mimic when using a source which is not a release. E.g. `coq.override { version = "d370a9d1328a4e1cdb9d02ee032f605a9d94ec7a"; coq-version = "8.10"; }`.

     

       
10
       
10
       
 
       


     

       
11
       
11
       
-
       
The associated package set can be optained using `mkCoqPackages coq`, where `coq` is the derivation to use.

     

       
11
       
11
       
+
       
The associated package set can be obtained using `mkCoqPackages coq`, where `coq` is the derivation to use.

     

       
12
       
12
       
 
       


     

       
13
       
13
       
 
       
## Coq packages attribute sets: `coqPackages` {#coq-packages-attribute-sets-coqpackages}

     

       
14
       
14
       
 
       


     

···

       
38
       
38
       
 
       


     

       
39
       
39
       
 
       
Nixpkgs tries to target support real architecture defaults based on the

     

       
40
       
40
       
 
       
CUDA toolkit version with PTX support for future hardware.  Experienced

     

       
41
       
41
       
-
       
users may optmize this configuration for a variety of reasons such as

     

       
41
       
41
       
+
       
users may optimize this configuration for a variety of reasons such as

     

       
42
       
42
       
 
       
reducing binary size and compile time, supporting legacy hardware, or

     

       
43
       
43
       
 
       
optimizing for specific hardware.

     

       
44
       
44
       
 
       


     

···

       
37
       
37
       
 
       
```

     

       
38
       
38
       
 
       


     

       
39
       
39
       
 
       
- The first parameter is the Cue schema file.

     

       
40
       
40
       
-
       
- The second paramter is an options parameter, currently, only: `document` can be passed.

     

       
40
       
40
       
+
       
- The second parameter is an options parameter, currently, only: `document` can be passed.

     

       
41
       
41
       
 
       


     

       
42
       
42
       
-
       
`document` : match your input data against this fragment of structure or definition, e.g. you may use the same schema file but differents documents based on the data you are validating.

     

       
42
       
42
       
+
       
`document` : match your input data against this fragment of structure or definition, e.g. you may use the same schema file but different documents based on the data you are validating.

     

       
43
       
43
       
 
       


     

       
44
       
44
       
 
       
Another example, given the following `validator.nix` :

     

       
45
       
45
       
 
       
```

     

···

       
4
       
4
       
 
       


     

       
5
       
5
       
 
       
### Installation without packages {#installation-without-packages}

     

       
6
       
6
       
 
       


     

       
7
       
7
       
-
       
You can install `hy` via nix-env or by adding it to `configuration.nix` by reffering to it as a `hy` attribute. This kind of installation adds `hy` to your environment and it succesfully works with `python3`.

     

       
7
       
7
       
+
       
You can install `hy` via nix-env or by adding it to `configuration.nix` by referring to it as a `hy` attribute. This kind of installation adds `hy` to your environment and it successfully works with `python3`.

     

       
8
       
8
       
 
       


     

       
9
       
9
       
 
       
::: {.caution}

     

       
10
       
10
       
-
       
Packages that are installed with your python derivation, are not accesible by `hy` this way.

     

       
10
       
10
       
+
       
Packages that are installed with your python derivation, are not accessible by `hy` this way.

     

       
11
       
11
       
 
       
:::

     

       
12
       
12
       
 
       


     

       
13
       
13
       
 
       
### Installation with packages {#installation-with-packages}

     

···

       
3
       
3
       
 
       
         xml:id="chap-language-support">

     

       
4
       
4
       
 
       
 <title>Languages and frameworks</title>

     

       
5
       
5
       
 
       
 <para>

     

       
6
       
6
       
-
       
  The <link linkend="chap-stdenv">standard build environment</link> makes it easy to build typical Autotools-based packages with very little code. Any other kind of package can be accomodated by overriding the appropriate phases of <literal>stdenv</literal>. However, there are specialised functions in Nixpkgs to easily build packages for other programming languages, such as Perl or Haskell. These are described in this chapter.

     

       
6
       
6
       
+
       
  The <link linkend="chap-stdenv">standard build environment</link> makes it easy to build typical Autotools-based packages with very little code. Any other kind of package can be accommodated by overriding the appropriate phases of <literal>stdenv</literal>. However, there are specialised functions in Nixpkgs to easily build packages for other programming languages, such as Perl or Haskell. These are described in this chapter.

     

       
7
       
7
       
 
       
 </para>

     

       
8
       
8
       
 
       
 <xi:include href="agda.section.xml" />

     

       
9
       
9
       
 
       
 <xi:include href="android.section.xml" />

     

···

       
605
       
605
       
 
       
`test` command for a `checkPhase` which runs `pytest`. This is also beneficial

     

       
606
       
606
       
 
       
when a package may need many items disabled to run the test suite.

     

       
607
       
607
       
 
       


     

       
608
       
608
       
-
       
Using the example above, the analagous `pytestCheckHook` usage would be:

     

       
608
       
608
       
+
       
Using the example above, the analogous `pytestCheckHook` usage would be:

     

       
609
       
609
       
 
       


     

       
610
       
610
       
 
       
```

     

       
611
       
611
       
 
       
  checkInputs = [ pytestCheckHook ];

     
···

       
624
       
624
       
 
       
  ];

     

       
625
       
625
       
 
       
```

     

       
626
       
626
       
 
       


     

       
627
       
627
       
-
       
This is expecially useful when tests need to be conditionally disabled,

     

       
627
       
627
       
+
       
This is especially useful when tests need to be conditionally disabled,

     

       
628
       
628
       
 
       
for example:

     

       
629
       
629
       
 
       


     

       
630
       
630
       
 
       
```

     

···

       
319
       
319
       
 
       
However, please check if it's possible to disable a problematic subset of the

     

       
320
       
320
       
 
       
test suite and leave a comment explaining your reasoning.

     

       
321
       
321
       
 
       


     

       
322
       
322
       
-
       
This can be achived with `--skip` in `checkFlags`:

     

       
322
       
322
       
+
       
This can be achieved with `--skip` in `checkFlags`:

     

       
323
       
323
       
 
       


     

       
324
       
324
       
 
       
```nix

     

       
325
       
325
       
 
       
rustPlatform.buildRustPackage {

     

···

       
303
       
303
       
 
       
This is used by the Nix build process to set the dynamic linker, glibc

     

       
304
       
304
       
 
       
in the case of i686-linux using the default Nix packages collection.

     

       
305
       
305
       
 
       


     

       
306
       
306
       
-
       
Obiously, since we need to compile libstc++ for arm-linux with uClibc linking

     

       
306
       
306
       
+
       
Obviously, since we need to compile libstc++ for arm-linux with uClibc linking

     

       
307
       
307
       
 
       
will not be done correctly: you can't link object files built for arm-linux

     

       
308
       
308
       
 
       
with a glibc built for i686-linux.

     

       
309
       
309
       
 
       


     

···

       
29
       
29
       
 
       
`nix-env` lacks an easy way to select the outputs to install. When installing a package, `nix-env` always installs the outputs listed in `meta.outputsToInstall`, even when the user explicitly selects an output.

     

       
30
       
30
       
 
       


     

       
31
       
31
       
 
       
::: {.warning}

     

       
32
       
32
       
-
       
`nix-env` silenty disregards the outputs selected by the user, and instead installs the outputs from `meta.outputsToInstall`. For example,

     

       
32
       
32
       
+
       
`nix-env` silently disregards the outputs selected by the user, and instead installs the outputs from `meta.outputsToInstall`. For example,

     

       
33
       
33
       
 
       


     

       
34
       
34
       
 
       
```ShellSession

     

       
35
       
35
       
 
       
$ nix-env -iA nixpkgs.coreutils.info

     

···

       
719
       
719
       
 
       


     

       
720
       
720
       
 
       
##### `dontStripHost` {#var-stdenv-dontStripHost}

     

       
721
       
721
       
 
       


     

       
722
       
722
       
-
       
Like `dontStrip`, but only affects the `strip` command targetting the package’s host platform. Useful when supporting cross compilation, but otherwise feel free to ignore.

     

       
722
       
722
       
+
       
Like `dontStrip`, but only affects the `strip` command targeting the package’s host platform. Useful when supporting cross compilation, but otherwise feel free to ignore.

     

       
723
       
723
       
 
       


     

       
724
       
724
       
 
       
##### `dontStripTarget` {#var-stdenv-dontStripTarget}

     

       
725
       
725
       
 
       


     

       
726
       
726
       
-
       
Like `dontStrip`, but only affects the `strip` command targetting the packages’ target platform. Useful when supporting cross compilation, but otherwise feel free to ignore.

     

       
726
       
726
       
+
       
Like `dontStrip`, but only affects the `strip` command targeting the packages’ target platform. Useful when supporting cross compilation, but otherwise feel free to ignore.

     

       
727
       
727
       
 
       


     

       
728
       
728
       
 
       
##### `dontMoveSbin` {#var-stdenv-dontMoveSbin}

     

       
729
       
729