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

Support cabal new-build #63

Open
ivanperez-keera opened this issue Apr 16, 2018 · 2 comments
Open

Support cabal new-build #63

ivanperez-keera opened this issue Apr 16, 2018 · 2 comments

Comments

@ivanperez-keera
Copy link
Owner

Apparently, something needs to change to support this.

PR #62 Needs to be split in two, one for this issue and one for issue #61 .

@ivanperez-keera
Copy link
Owner Author

It seems that some people do not include the cabal.project file in the repo. instead, they ignore it:

See https://github.com/haskell-hvr/uuid/blob/6591726483cbef136c836d32445807a63b1ff265/.gitignore

Any thoughts?

@Rizary
Copy link
Contributor

Rizary commented Apr 17, 2018

cabal.project.local and cabal.project are different. They do include the cabal.project, but not cabal.project.local. cabal new-configure will create cabal.project.local, its purpose is:

  • When you depend on a library that's not part of the same project, is available on a local filesystem, and won't necessarily be in the same absolute or relative location on every developer's machine.
  • When you want to locally override an existing dependency to specify a WIP version of that dependency either on the local filesystem or in a VCS

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

Successfully merging a pull request may close this issue.

2 participants