-
Notifications
You must be signed in to change notification settings - Fork 710
Update CONTRIBUTING.md
with Nix developer shell instructions
#9218
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
Conversation
See #8753 |
Summarising the discussion in the issue linked above. There is little appetite to have a nix setup in this repository. This kind of things tend to get bit-rotten [^1] and they are trivial to maintain externally. Indeed all you are proposing here can be obtained with a one-liner:
Nevertheless (IIRC) the consensus was that it would ok to add such one liner (as a merge suggestion) to https://github.com/haskell/cabal/blob/master/CONTRIBUTING.md. [^1] there's bunch of dockerfiles in the repo, does anybody use them? I appreciate your contribution but I suggest closing this. |
4abefb3
to
a0ba872
Compare
@yvan-sraka Do you think it would be better to have a flake hosted somewhere else? I'm thinking about dependency pinning for instance, because fourmolu needs to be one exact version. |
I've discarded my previous commit and updated the |
I don't know, but it would be really easy to just copy this flake or that one in another repo, and then you can use e.g. |
@yvan-sraka I think I'd be in favour of pointing to your flake, especially if it means a better, more principled approach. |
73c19ad
to
1aa4e06
Compare
I've updated the PR (and edited its description to align with the changes) :) |
CONTRIBUTING.md
with Nix developer shell instructions
cf25353
to
d737d71
Compare
This PR does not modify the
cabal
behavior. It only updates theCONTRIBUTING.md
documentation with instructions on setting up a Nix developer shell. I believe this could help some newcomers get started more easily to contribute to the project.Rendered
Checklist: