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

Improving GHC environment file related errors #8540

Open
noughtmare opened this issue Oct 20, 2022 · 1 comment
Open

Improving GHC environment file related errors #8540

noughtmare opened this issue Oct 20, 2022 · 1 comment
Labels
cabal-install: environment-files re: error-message Concerning error messages delivered to the user re: install --lib Concerning `cabal install --lib`

Comments

@noughtmare
Copy link
Collaborator

Inspired by this stackoverflow question,

When running commands such as cabal install --lib bytestring the result may depend on what is already in the default environment file. However, cabal will not really tell you that. It only says things like:

bytestring-0.10.12.1 (constraint from user target requires ==0.10.12.0)

And

bytestring-0.10.12.0 (constraint from user target requires ==0.11.3.1)

I think it would be good to show exactly where these constraints come from, e.g. with file names and line numbers.

Also I think it would be useful to have a general warning/info message about which environment files are used.

@noughtmare noughtmare changed the title Improving of GHC environment file related errors Improving GHC environment file related errors Oct 20, 2022
@noughtmare
Copy link
Collaborator Author

I guess this is related to #7820.

@noughtmare noughtmare added the re: error-message Concerning error messages delivered to the user label Oct 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cabal-install: environment-files re: error-message Concerning error messages delivered to the user re: install --lib Concerning `cabal install --lib`
Projects
None yet
Development

No branches or pull requests

2 participants