Merge commit 59f9c6722b into haskell-updates
This commit is contained in:
@@ -6,7 +6,7 @@ compiler. It includes an interactive mode and a custom package format, "eggs".
|
||||
|
||||
## Using Eggs {#sec-chicken-using}
|
||||
|
||||
Eggs described in nixpkgs are available inside the
|
||||
Eggs described in Nixpkgs are available inside the
|
||||
`chickenPackages.chickenEggs` attrset. Including an egg as a build input is
|
||||
done in the typical Nix fashion. For example, to include support for [SRFI
|
||||
189](https://srfi.schemers.org/srfi-189/srfi-189.html) in a derivation, one
|
||||
@@ -26,7 +26,7 @@ variables `CHICKEN_INCLUDE_PATH` and `CHICKEN_REPOSITORY_PATH`.
|
||||
|
||||
## Updating Eggs {#sec-chicken-updating-eggs}
|
||||
|
||||
nixpkgs only knows about a subset of all published eggs. It uses
|
||||
Nixpkgs only knows about a subset of all published eggs. It uses
|
||||
[egg2nix](https://github.com/the-kenny/egg2nix) to generate a
|
||||
package set from a list of eggs to include.
|
||||
|
||||
|
||||
@@ -111,7 +111,7 @@ Fortunately, we have a [family of hooks]{#ssec-gnome-hooks-wrapgappshook} that a
|
||||
- [`wrapGAppsHook4`]{#ssec-gnome-hooks-wrapgappshook4} for GTK 4 apps. Same as `wrapGAppsHook3` but replaces `gtk3` with `gtk4`.
|
||||
- [`wrapGAppsNoGuiHook`]{#ssec-gnome-hooks-wrapgappsnoguihook} for programs without a graphical interface. Same as the above but does not bring `gtk3` and `librsvg` into the closure.
|
||||
|
||||
The hooks do the the following:
|
||||
The hooks do the following:
|
||||
|
||||
- `wrapGApps*` hook itself will add the package’s `share` directory to `XDG_DATA_DIRS`.
|
||||
|
||||
|
||||
@@ -542,7 +542,7 @@ set `prePnpmInstall` to the right commands to run. For example:
|
||||
```nix
|
||||
{
|
||||
prePnpmInstall = ''
|
||||
pnpm config set dedupe-peer-dependants false
|
||||
pnpm config set dedupe-peer-dependents false
|
||||
'';
|
||||
pnpmDeps = pnpm.fetchDeps {
|
||||
inherit (finalAttrs) prePnpmInstall;
|
||||
|
||||
@@ -52,7 +52,7 @@ Here is a simple package example.
|
||||
|
||||
- It sets the optional `doCheck` attribute such that tests will be run with
|
||||
`dune runtest -p angstrom` after the build (`dune build -p angstrom`) is
|
||||
complete, but only if the OCaml version is at at least `"4.05"`.
|
||||
complete, but only if the OCaml version is at least `"4.05"`.
|
||||
|
||||
- It uses the package `ocaml-syntax-shims` as a build input, `alcotest` and
|
||||
`ppx_let` as check inputs (because they are needed to run the tests), and
|
||||
|
||||
@@ -1018,7 +1018,7 @@ that we introduced with the `let` expression.
|
||||
#### Handling dependencies {#handling-dependencies}
|
||||
|
||||
Our example, `toolz`, does not have any dependencies on other Python packages or system libraries.
|
||||
[`buildPythonPackage`](#buildpythonpackage-function) uses the the following arguments in the following circumstances:
|
||||
[`buildPythonPackage`](#buildpythonpackage-function) uses the following arguments in the following circumstances:
|
||||
|
||||
- `dependencies` - For Python runtime dependencies.
|
||||
- `build-system` - For Python build-time requirements.
|
||||
|
||||
Reference in New Issue
Block a user