Commit 5eab6a0d authored by Edward Z. Yang's avatar Edward Z. Yang Committed by Ben Gamari
Browse files

Document meaning of order of --package-db flags, fixes #12485.

Test Plan: none

Reviewers: austin, niteria, bgamari

Reviewed By: niteria

Subscribers: thomie

Differential Revision: https://phabricator.haskell.org/D2514

GHC Trac Issues: #12485
parent feaa31fb
...@@ -384,6 +384,11 @@ stack. Several command line options described below can further manipulate this ...@@ -384,6 +384,11 @@ stack. Several command line options described below can further manipulate this
initial stack. You can see GHC's effective package database stack by running initial stack. You can see GHC's effective package database stack by running
GHC with the :ghc-flag:`-v` flag. GHC with the :ghc-flag:`-v` flag.
This stack structure means that the order of :ghc-flag:`-package-db` flags or
:envvar:`GHC_PACKAGE_PATH` is important. Each substack of the stack
must be well formed (packages in databases on top of the stack can refer
to packages below, but not vice versa).
*Package shadowing:* When multiple package databases are in use it *Package shadowing:* When multiple package databases are in use it
is possible, though rarely, that the same installed package id is present in is possible, though rarely, that the same installed package id is present in
more than one database. In that case, packages closer to the top of the stack more than one database. In that case, packages closer to the top of the stack
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment