-
Notifications
You must be signed in to change notification settings - Fork 704
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 repl --allow-newer #1835
Comments
This is a wider issue. For example, |
I agree that this is a wider issue — and maybe even wider than that. Basically, with these recent changes to cabal build/test/etc it's become very hard to understand in advance whether a given cabal command:
let alone to control that! I'd love to see this problem addressed in a consistent way across different commands. |
I agree. My end goal is that people should never have to run configure nor install dependencies manually, which means all commands that need to imply configure will imply configure (and configure will mostly be an implementation detail). Similarly for installing dependencies. The latter will unfortunately have to be limited to sandboxes for now, as it's too dangerous to automatically install packages in the user/global package DB. |
A similar issue: |
I'd love to see proper support for
|
Just stumbled on this.. I'd say it's also a bug since it prevents --build-depends from working |
Closed with Please, reopen if not. |
cabal repl
doesn't understand--allow-newer
, so I had to runcabal configure --allow-newer
, thencabal repl
.The text was updated successfully, but these errors were encountered: