| 26 Apr 2026 |
 eldritchcookie | can cabal v1-build build only some select components? i would ideally have a method that works with multiple public libraries | 12:53:29 |
 andromeda | I am building a package with pkgs.haskellPackages.callCabal2nix. I assume it doesn't have the capability to fetch+build source-repository-package es in cabal.project? | 13:25:26 |
| andromeda | * I am building a package with pkgs.haskellPackages.callCabal2nix. I assume it doesn't have the capability to fetch+build source-repository-packages in cabal.project? | 13:25:34 |
 alexfmpe | callCabal2nix ignores cabal.project | 14:11:22 |
| alexfmpe | so you'd need to either duplicate that override, or maybe do something like a git submodule to keep single source of truth (never tried the later method) | 14:12:08 |
| alexfmpe | hackage.nix lets you take cabal.project into account, and also use the solver, but it's an entirely different beast | 14:12:32 |
| alexfmpe | a more heavy handed workaround mentioned in there involves a flag to decide whether to specify build-tool-depends so you can skip it when using shellFor and let cabal get it from path there | 14:15:14 |
| alexfmpe | nix-build worked for me on your repo, it's the integration between shellFor and cabal-install where things go wrong | 14:15:49 |
| andromeda | In reply to @alexfmpe:matrix.org
hackage.nix lets you take cabal.project into account, and also use the solver, but it's an entirely different beast what makes that an entirely different beast? | 14:17:44 |
| alexfmpe | https://input-output-hk.github.io/haskell.nix/motivation.html#comparison-with-nixpkgs | 14:18:25 |
| alexfmpe | that's somewhat outdated, it's not necessarily better for cross, but the rest stands | 14:19:00 |
| andromeda | that... seems like overkill. I'mma go with keeping the cabal.project in sync enough with the flake. | 14:21:01 |
 sterni (he/him) | cabal-install v2 commands expect build-tool-depends to be registered in the package db which Nix environments don't do because it is wrong from the perspective of the dependency separation: build tools go to nativeBuildInputs and not into (propagated)BuildInputs. Only the latter get folded into the package db. There is an open issue about this. Only affects developer environments.
Easiest workaround is to use the cabal-install v1 commands which check PATH for tools as well. | 14:33:49 |
| sterni (he/him) | ah alex already answered, nvm. | 14:34:29 |
| sterni (he/him) | aiya: I bumped Hackage two days ago, you can follow the progress there: https://github.com/NixOS/nixpkgs/pull/510883. Giving a timeline is hard, but the answer is weeks unfortunately at the moment. | 14:36:14 |
 aiya | sterni i see, so maybe it is worth fixing, could you please elaborate on your latest comment here (https://github.com/NixOS/nixpkgs/pull/506489#discussion_r3110806985)? apologies, i don't fully understand it | 20:02:42 |
| 20 May 2021 |
|  @grahamc:nixos.org set the history visibility to "world_readable". | 22:10:58 |
| @grahamc:nixos.org changed the room name to "" from "". | 22:10:58 |
| @grahamc:nixos.org invited  maralorn. | 22:11:05 |
| maralorn joined the room. | 22:11:13 |
|  andi- joined the room. | 22:30:49 |
| @grahamc:nixos.orgchanged room power levels. | 22:36:42 |
| Room Avatar Renderer. | 22:46:20 |
| maralorn changed the join rule to "public" from "public". | 22:54:26 |
| maralorn changed the room topic to "For discussions and questions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs | Current Docs: https://haskell4nix.readthedocs.io/" from "For discussions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs | Current Docs: https://haskell4nix.readthedocs.io/". | 22:56:19 |
|  Server Stats Discoverer (traveler bot) joined the room. | 23:05:49 |
|  pennae joined the room. | 23:06:26 |
|  justinrestivo joined the room. | 23:07:39 |
|  srid joined the room. | 23:07:41 |
|  bqv joined the room. | 23:08:26 |
