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

cabal new-build --package-db=foo doesn't do anything #5773

Closed
phadej opened this issue Dec 4, 2018 · 0 comments · Fixed by #7676
Closed

cabal new-build --package-db=foo doesn't do anything #5773

phadej opened this issue Dec 4, 2018 · 0 comments · Fixed by #7676

Comments

@phadej
Copy link
Collaborator

phadej commented Dec 4, 2018

if foo doesn't exist: builds
if foo exists: doesn't consider it.

I think that for 3.0 we should either remove package database flags from new-build commands; or teach these commands to use other package databases. I.e. to consider other, not only global database. I actually have a use case for this. ("obviously", if I use some weird --package-db, I'd use my own --store-dir etc. so this is intended for people who know what they are doing).

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.

1 participant