Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

haskell.nix integration #615

Draft
wants to merge 26 commits into
base: main
Choose a base branch
from
Draft

haskell.nix integration #615

wants to merge 26 commits into from

Conversation

walkah
Copy link
Member

@walkah walkah commented Jun 24, 2022

Another VERY WIP EXPERIMENT using haskell.nix to build proper nix packages for fission cli + server.

Known issues:

  • Builds a lot of stuff (there is no binary cache for aarch64-darwin at all, and minimal stuff on x86_64 platforms)
  • current stack-based build / install workflow doesn't work (only nix build)

@tennox
Copy link
Contributor

tennox commented Jul 16, 2022

I forgot to check first if an existing PR is doing what I was doing, so I duplicated this: #623 🙈

But then, checking your checklist of known issues, I think I managed to not break the existing workflow - stack build still works fine in the devshell.

I also managed to use the binary cache (linux x86_64), at least for the basics (like ghc) - the haskell packages themselves still took quite some time to build. But this is the same with stack build (for me)?

Maybe you check it out yourself? As I never actually used a stack-based haskell workflow and I'm not too sure about it.

@walkah
Copy link
Member Author

walkah commented Jul 16, 2022

I also managed to use the binary cache (linux x86_64), at least for the basics (like ghc) - the haskell packages themselves still took quite some time to build. But this is the same with stack build (for me)?

totally right! I was tinkering with two approaches in parallel ... I've rebased against the dev setup in main and it looks like it's all working pretty well. thanks for poking around! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants