Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Dec 7, 2014
  1. Updated INSTALL on building man pages.

    Closes #1788.
Commits on Jun 18, 2014
  1. Removed old haddock reader code. Add dependency on haddock-library.

    This also removes the dependency on alex and happy.
Commits on May 19, 2014
  1. Removed dependency on conduit.

    * http-conduit flag is now https.
    * Instead of http-conduit, we depend on http-client and http-client-tls.
Commits on Sep 20, 2013
Commits on Aug 31, 2013
Commits on Aug 16, 2013
  1. Improved INSTALL instructions:

    * Note binary package for OSX.
    * Added URL of github wiki page on installing the dev version.
Commits on Aug 8, 2013
  1. Improved INSTALL instructions.

Commits on Jul 20, 2013
  1. Added info about CABALDIR.

    Modified from a patch by achalddave.
Commits on Jan 24, 2013
  1. Use hsb2hs preprocessor instead of TH for embed_data_files.

    This should work on Windows, unlike the TH solution with
Commits on Dec 30, 2012
  1. Updated INSTALL with new flags.

Commits on Jul 26, 2012
Commits on Apr 27, 2012
Commits on Feb 10, 2012
Commits on Jan 21, 2012
Commits on Dec 22, 2011
Commits on Aug 19, 2011
Commits on Nov 24, 2010
Commits on Jul 21, 2010
  1. Reintroduced 'library' cabal flag.

    It is needed for the Windows installer, since if a library
    is produced, the binary can't be made relocatable.
Commits on Apr 10, 2010
  1. Removed 'library' Cabal flag.

    Reason: starting with Cabal 1.8, installing pandoc with '-library
    +executable' did not work, since the build-depends in the Library
    stanza were ignored. The problem could be solved by repeating the
    build-depends in the Executable stanza, but this seems non-ideal
    (and might lead to errors later on).  The '-library' option isn't
    so useful anyway, since to compile pandoc in the first place, you
    need a large number of Haskell libraries installed, and in this
    case, why balk at another? It was chiefly intended for packagers,
    but packagers will need to use a chroot environment anyway, and
    they can then simply copy the executable and not the library.
    Thanks to Jim Pryor for calling the problem to my attention
    in connection with an arch linux package.
Something went wrong with that request. Please try again.