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: configuration-ghc-8.0.x.nix: keep inline-c at 0.5.6.1 #33271

Merged
merged 1 commit into from Jan 2, 2018

Conversation

basvandijk
Copy link
Member

Motivation for this change

inline-c > 0.5.6.1 requires template-haskell >= 2.12 which is not available on ghc-8.0 so we keep inline-c at 0.5.6.1 and inline-c-cpp at 0.1.0.0.

@peti I know I shouldn't edit hackage-packages.nix so where should I place the inline-c_0_5_6_1 and inline-c-cpp_0_1_0_0 definitions?

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@peti
Copy link
Member

peti commented Jan 1, 2018

Where should I place the inline-c_0_5_6_1 and inline-c-cpp_0_1_0_0 definitions?

Add the appropriate versions to the extra-packages section in pkgs/development/haskell-modules/configuration-hackage2nix.yaml. Then these versions will appear in hackage-packages.nix the next time we merge the update branch (i.e. every couple of days).

@basvandijk
Copy link
Member Author

Ok thanks, I added the versions to configuration-hackage2nix.yaml.

I guess I can leave the additions in hackage-packages.nix because then this PR can be merged immediately without having to wait for the next generation.

@peti peti merged commit b1fd018 into NixOS:master Jan 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants