X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=ghc%2Fdocs%2Fusers_guide%2Fpackages.xml;h=3bd65c66ce8c2c19ae837a20a5acf3fb59e7e309;hb=0a1d263163f12502405b191895fffe48e47b2dfc;hp=b955f00fc23e9410ab21eca36d31b6ecf12a375b;hpb=c79b72163e7f4020a3f37bec7499af5ac21d7884;p=ghc-hetmet.git
diff --git a/ghc/docs/users_guide/packages.xml b/ghc/docs/users_guide/packages.xml
index b955f00..3bd65c6 100644
--- a/ghc/docs/users_guide/packages.xml
+++ b/ghc/docs/users_guide/packages.xml
@@ -298,6 +298,7 @@ $ export GHC_PACKAGE_PATH=$HOME/.my-ghc-packages.conf:
To check whether your GHC_PACKAGE_PATH setting
is doing the right thing, ghc-pkg list will list all
the databases in use, in the reverse order they are searched.
+
@@ -403,6 +404,15 @@ $ export GHC_PACKAGE_PATH=$HOME/.my-ghc-packages.conf:
options are given, the rightmost one is used as the database to act
upon.
+ If the environment variable GHC_PACKAGE_PATH is
+ set, and its value does not end in a separator (: on
+ Unix, ; on Windows), then the last database is
+ considered to be the global database, and will be modified by default by
+ ghc-pkg. The intention here is that
+ GHC_PACKAGE_PATH can be used to create a virtual
+ package environment into which Cabal packages can be installed without
+ setting anything other than GHC_PACKAGE_PATH.
+
The ghc-pkg program may be run in the ways listed
below. Where a package name is required, the package can be named in
full including the version number