From bab4ae80cc5b14926896ea3d5f5ac4db5bb80035 Mon Sep 17 00:00:00 2001 From: "Edward Z. Yang" Date: Sun, 1 Jan 2017 09:41:45 -0800 Subject: Fix incorrect statement about plugin packages. Signed-off-by: Edward Z. Yang --- docs/users_guide/extending_ghc.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/users_guide/extending_ghc.rst') 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: -- cgit v1.2.1