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

Add a deprecation warning when using cabal-dev interactively #110

Open
creswick opened this issue Sep 6, 2013 · 0 comments
Open

Add a deprecation warning when using cabal-dev interactively #110

creswick opened this issue Sep 6, 2013 · 0 comments

Comments

@creswick
Copy link
Owner

creswick commented Sep 6, 2013

I think we can begin to retire cabal-dev, with the recent release of cabal-install-1.18, which supports sandboxed builds and corresponding sandboxed ghci sessions.

Cabal-install now also provides a warning if you use cabal sandboxes for a project that has a cabal-dev directory, encouraging you to transition from cabal-dev.

I think we should do something similar, producing a warning when cabal-dev is invoked to indicate that cabal-install's sandboxes should be used instead. Here's one suggestion:

"""
Cabal-dev is deprecated with the release of cabal-1.18.
To create a sandbox with cabal-1.18, run:
$ cabal sandbox init
"""

I think we should endeavor to squelch this message if cabal-dev is /not/ running in an interactive environment, so we don't break any scripts that may rely on it's silence.

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

No branches or pull requests

1 participant