mirror of
https://github.com/simplex-chat/haskell.nix.git
synced 2026-06-03 09:17:32 +00:00
Domen Kožar
2852a9521f
* fix hackage and stackage to work * user-guides -> tutorials * Restructure tutorials * getting-started: clarify on packages and components * Update docs/tutorials/development.md Co-authored-by: Rodney Lorrimar <dev@rodney.id.au> * getting-started: bail out if cabal.project and stack.yaml are present * hackage-stackage: delete duplicated content Co-authored-by: Rodney Lorrimar <dev@rodney.id.au>
1.7 KiB
1.7 KiB
Mapping non-Haskell dependencies to Nixpkgs
Cabal files may contain dependencies to external non-Haskell dependencies via:
If there is a pkgs attribute in Nixpkgs that matches the name given
in the Cabal file, then it will be added as a dependency (see the
output of cabal-to-nix). Otherwise, there needs to be a mapping from
Cabal file names (decided by the package author) to Nix package
identifiers.
Nixpkgs overlay
The user may solve it by themself by overriding Nixpkgs and adding a package alias. For example:
nixpkgs.overlays = [
(self: super: {
icuuc = self.icu;
icui18n = self.icu;
icudata = self.icu;
})
];
Mapping in Haskell.nix
Alternatively, if the name is commonly used, an alias can be added to the Haskell.nix sources, so that it's solved for all users.
lib/pkgconf-nixpkgs-map.nix- forpkgconfig-dependslib/system-nixpkgs-map.nix- forbuild-tool-depends,frameworks,extra-libraries, etc.
!!! tip "Open a PR" Please go ahead and open a pull request to improve the package mappings.