Open dustinlacewell opened 3 years ago
Hi, I'm not a nix user. I use stack. Feel free to update the nix scripts. (the stack.yaml works, it can build the project)
I suppose the question is whether lambdacube will eventually see a modernization of its dependencies.
not now, but eventually sure.
Hi @csabahruska,
The way NixPkgs handles Haskell, for packages on Hackage, is basically just that it builds the packages that are on Hackage. As long as it compiles, there shouldn't be anything else needed.
So, currently with version 0.3.0.1 on Hackage, all I have to patch to get it to compile is fixing the Monoid/Semigroup thing and loosen the version bounds… I figured out what changes to make for that, so I was going to put in a PR.
Turns out, the code on GitHub is already updated! It just hasn't been published to Hackage so NixPkgs isn't picking it up.
If it's possible to publish the latest version to Hackage, I believe that should resolve this!
Building on Nix currently fails due to old dependencies no longer tracked on Nixpkgs:
It looks like the packages
aeson
,base
,containers
andvector
are too old to be built by Nix.So using a certain shell.nix was able to force it to build anyway:
But then it fails due to some error related to Semigroup:
Is it that lambdacube is simply targetting too old of a Haskell?