summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorEdward Z. Yang <ezyang@cs.stanford.edu>2016-09-05 19:19:57 -0400
committerBen Gamari <ben@smart-cactus.org>2016-09-08 10:43:57 -0400
commit5eab6a0da5f22a47d04b97a0ec8988346675b33b (patch)
tree3a21b65ced76a2650e360a07d849983960990e6b /docs
parentfeaa31fbc41685d69045ac8d34be4e18f4f27ffd (diff)
downloadhaskell-5eab6a0da5f22a47d04b97a0ec8988346675b33b.tar.gz
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
Diffstat (limited to 'docs')
-rw-r--r--docs/users_guide/packages.rst5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/users_guide/packages.rst b/docs/users_guide/packages.rst
index 15c97c73ae..d3da125d58 100644
--- a/docs/users_guide/packages.rst
+++ b/docs/users_guide/packages.rst
@@ -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
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
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