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

Reconfiguration avoidance not affected by library visibility change #6358

Open
fgaz opened this issue Nov 15, 2019 · 0 comments
Open

Reconfiguration avoidance not affected by library visibility change #6358

fgaz opened this issue Nov 15, 2019 · 0 comments

Comments

@fgaz
Copy link
Member

fgaz commented Nov 15, 2019

Describe the bug
Visibility of dependencies does not get taken into account when cabal chooses whether to reconfigure or not a component

To Reproduce
Steps to reproduce the behavior:

  • Project with two packages: a, b
  • b has a public sublibrary sublib
  • a component of a depends on b:sublib
  • cabal new-build all
  • make sublib private
  • cabal new-build all
  • a does not get reconfigured and there's no failure

Expected behavior

a gets reconfigured because of the change in b and the command fails

System information
cabal 3.0.0.0, ghc 8.8.1

@fgaz fgaz added the type: bug label Nov 15, 2019
@fgaz fgaz mentioned this issue Dec 15, 2020
31 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant