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

Warning: The install command is a part of the legacy v1 style of cabal usage. #48

Closed
awf opened this issue Jul 19, 2019 · 1 comment · Fixed by #49
Closed

Warning: The install command is a part of the legacy v1 style of cabal usage. #48

awf opened this issue Jul 19, 2019 · 1 comment · Fixed by #49

Comments

@awf
Copy link
Contributor

awf commented Jul 19, 2019

Following instructions on README

PS C:\dev\knossos\knossos-ksc> cabal install hspec parsec mtl hashable filepath
Warning: The install command is a part of the legacy v1 style of cabal usage.

Please switch to using either the new project style and the new-install
command or the legacy v1-install alias as new-style projects will become the
default in the next version of cabal-install. Please file a bug if you cannot
replicate a working v1- use case with the new-style commands.
...

Can we fix?

toelli-msft added a commit that referenced this issue Jul 19, 2019
There's no need to separately install packages since they will be installed
by cabal v2-repl.

Fixes #48
@toelli-msft
Copy link
Contributor

It's a warning not an error and it is OK to ignore it. Nothing will break imminently.

The proper fix is to use cabal v2-repl instead of ghci. See #49

toelli-msft added a commit that referenced this issue Jul 19, 2019
There's no need to separately install packages since they will be installed
by cabal v2-repl.

Fixes #48
toelli-msft added a commit that referenced this issue Jul 19, 2019
There's no need to separately install packages since they will be installed
by cabal v2-repl.

Fixes #48
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

Successfully merging a pull request may close this issue.

2 participants