Changes between Version 15 and Version 16 of Debugging/InstallingPackagesInplace


Ignore:
Timestamp:
Nov 23, 2012 9:53:52 AM (3 years ago)
Author:
danielv
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Debugging/InstallingPackagesInplace

    v15 v16  
    1919 * This will install the package in your home directory (e.g. somewhere under `~/.cabal/lib` on a Unix system), and it will register the package in your private package database, so you'll probably want to remove and unregister it by hand when you've finished.
    2020
    21 Plan A can fail, because sometimes GHC changes require corresponding Cabal changes (this happened in GHC 6.12), so you might get a message like
     21Plan A can fail, because sometimes GHC changes require corresponding Cabal changes (this happened in GHC 6.12, and after the GHC 7.6.1 release). If the format changed you might get a message like
    2222{{{
    2323cabal: failed to parse output of 'ghc-pkg dump'
    2424}}}
    25 In that case you need to use the Cabal code that comes with the new version of GHC (ie the one in your build tree).  So use Plan B.
     25But incompatibility can result in other problems installing packages. In that case you need to use the Cabal code that comes with the new version of GHC (ie the one in your build tree).  So use Plan B.
    2626
    2727== Plan B: use the Cabal library bundled with GHC ==