Ticket #4072 (closed bug: fixed)
Local package DB doesn't take preference over global DB
| Reported by: | tibbe | Owned by: | simonmar |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.12.3 |
| Component: | Package system | Version: | 6.12.1 |
| Keywords: | Cc: | ||
| Operating System: | Unknown/Multiple | Architecture: | Unknown/Multiple |
| Type of failure: | None/Unknown | Difficulty: | |
| Test Case: | Blocked By: | ||
| Blocking: | Related Tickets: |
Description
I sometime find myself wanting to compile some small test program (say Test.hs) against a locally built Cabal package. Here's what I do:
ghc -c Test.hs -package-conf dist/package.conf.inplace
This doesn't work
Test.hs:4:0:
Failed to load interface for `Data.Text.Lazy.Builder':
Use -v to see a list of the files searched for.
The global version of text gets picked instead of the local one (and in this case the global version lacks the Data.Text.Lazy.Builder module). I expect the package given on the command line to take preference.
Workaround: Bump the version number of the local package.
Change History
Note: See
TracTickets for help on using
tickets.
