diff options
| author | Edward Z. Yang <ezyang@cs.stanford.edu> | 2017-01-01 09:41:45 -0800 |
|---|---|---|
| committer | Edward Z. Yang <ezyang@cs.stanford.edu> | 2017-01-01 09:44:03 -0800 |
| commit | bab4ae80cc5b14926896ea3d5f5ac4db5bb80035 (patch) | |
| tree | 8744ab1ee5c2e7bd93752b7f8ff9787e0949c110 | |
| parent | a3704409acc3bd237d3e872f640686918fb51f5f (diff) | |
| download | haskell-bab4ae80cc5b14926896ea3d5f5ac4db5bb80035.tar.gz | |
Fix incorrect statement about plugin packages.
Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
| -rw-r--r-- | docs/users_guide/extending_ghc.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/users_guide/extending_ghc.rst b/docs/users_guide/extending_ghc.rst index c02c93fac1..10c1b3d8c2 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: |