[commit: ghc] master: Fix incorrect statement about plugin packages. (bab4ae8)

[git at git.haskell.org]

Repository : ssh://git@git.haskell.org/ghc

On branch  : master
Link       : http://ghc.haskell.org/trac/ghc/changeset/bab4ae80cc5b14926896ea3d5f5ac4db5bb80035/ghc

>---------------------------------------------------------------

commit bab4ae80cc5b14926896ea3d5f5ac4db5bb80035
Author: Edward Z. Yang <ezyang at cs.stanford.edu>
Date:   Sun Jan 1 09:41:45 2017 -0800

    Fix incorrect statement about plugin packages.
    
    Signed-off-by: Edward Z. Yang <ezyang at cs.stanford.edu>


>---------------------------------------------------------------

bab4ae80cc5b14926896ea3d5f5ac4db5bb80035
 docs/users_guide/extending_ghc.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/users_guide/extending_ghc.rst b/docs/users_guide/extending_ghc.rst
index c02c93f..10c1b3d 100644
--- a/docs/users_guide/extending_ghc.rst
+++ b/docs/users_guide/extending_ghc.rst
@@ -259,10 +259,10 @@ control specifically plugin packages:
     need to be explicitly exposed using
     :ghc-flag:`-plugin-package` options.
 
-To declare a dependency on a plugin, add it to the ``ghc-plugins`` field
-in Cabal.  You should only put a plugin in ``build-depends`` if you
-require compatibility with older versions of Cabal, or also have a source
-import on the plugin in question.
+At the moment, the only way to specify a dependency on a plugin
+in Cabal is to put it in ``build-depends`` (which uses the conventional
+:ghc-flag:`-package-id` flag); however, in the future there
+will be a separate field for specifying plugin dependencies specifically.
 
 .. _writing-compiler-plugins: