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

Advice on distributing cabal.project.freeze for projects with exes and libs. #5750

Open
philderbeast opened this issue Nov 28, 2018 · 2 comments

Comments

@philderbeast
Copy link
Collaborator

For end-user executables, it is recommended that you distribute the
``cabal.project.freeze`` file in your source repository so that all
users see a consistent set of dependencies. For libraries, this is not
recommended: users often need to build against different versions of
libraries than what you developed against.

I don't know how to apply this advice when the project has both executables and libraries. Can we advise what to do in this situation too please? Can the constraints be limited to just the executables?

@philderbeast
Copy link
Collaborator Author

Would having --project=cabal-exes.project and --project=cabal-libs.project when cabal-exes.project.freeze exists but cabal-libs.project.freeze doesn't be consistent with the advice?

@jneira
Copy link
Member

jneira commented Mar 23, 2022

Issues related: #8047, #8059. Maybe #8053 could include the clarification

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

No branches or pull requests

2 participants