cafkafk/nixpkgs
cafkafk/nixpkgs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

Merge pull request #210984 from maralorn/haskell-docs-fix

Browse source 
haskell/docs: Fix a link
This commit is contained in:
maralorn 2023-01-15 22:19:36 +01:00 committed by GitHub
commit 98675d9744
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/languages-frameworks/haskell.section.md
View file

@ -159,13 +159,12 @@ on Hackage and tries to pick for every (transitive) dependency of your build
exactly one version. Those versions need to satisfy all the version constraints exactly one version. Those versions need to satisfy all the version constraints
given in the `.cabal` file of your package and all its dependencies. given in the `.cabal` file of your package and all its dependencies.
The Haskell builder in nixpkgs, (described in more detail in The [Haskell builder in nixpkgs](#haskell-mkderivation) does no such thing.
[#haskell-mkderivation]), does no such thing. It will simply take as input It will simply take as input packages with names off the desired dependencies
packages with names off the desired dependencies and just check whether they and just check whether they fulfill the version bounds and (by default, see
fulfill the version bounds and (by default, see `jailbreak`) fail if they `jailbreak`) fail if they don’t.
don’t.
The package resolution is done by the `haskellPackages.callPackage` function, The package resolution is done by the `haskellPackages.callPackage` function
which will, e.g., use `haskellPackages.aeson` for a package input of name which will, e.g., use `haskellPackages.aeson` for a package input of name
`aeson`. `aeson`.
While this is the default behavior, it is possible to override the dependencies While this is the default behavior, it is possible to override the dependencies