Skip to content
Commits on Aug 13, 2015
Commits on Jul 5, 2015
  1. Make cabal require hsb2hs >= 0.3.1.

    This is done by adding `hookedPrograms` in `Setup.hs`,
    which allows us to include `hsb2hs` in Build-Tools in cabal.
Commits on Jul 3, 2015
  1. Added pandoc.1 to repository. Don't build as part of cabal build.

    The process was too fragile.  It made too many assumptions about
    available libraries (which failed sometimes when sandboxes were
    used).  This is a low-tech solution.  The only drawback is that
    `man/pandoc.1` is a generated file in the repository.  It will need
    to be regenerated periodically when README changes.
Commits on Jul 2, 2015
Commits on Jul 1, 2015
  1. Generate man page in cabal build process and include in data/.

    The pandoc.1 man page is generated automatically after the cabal
    build process.  It goes in `data/pandoc.1`.  It can be obtained
    by the user who installs pandoc via cabal thus:
        pandoc --print-default-data-file pandoc.1 > pandoc.1
  2. New method for building man pages.

    + Removed `--man1`, `--man5` options (breaking change).
    + Removed `Text.Pandoc.ManPages` module (breaking API change).
    + Version bump to 1.15 because of the breaking changes, even
      though they involve features that have only been in pandoc
      for a day.
    + Makefile target for `man/man1/pandoc.1`.  This uses pandoc to
      create the man page from README using a custom template and filters.
    + Added `man/` directory with template and filters needed to build
      man page.
    + We no longer have two man pages: pandoc.1 and pandoc_markdown.5.
      Now there is just pandoc.1, which has all the content from README.
      This change was needed because of the extensive cross-references
      between parts of the README.
    + Removed old `data/pandoc.1.template` and
Commits on Jun 28, 2015
  1. New method for producing man pages.

    This change adds `--man1` and `--man5` options to pandoc, so
    pandoc can generate its own man pages.
    It removes the old overly complex method of building a separate
    executable (but not installing it) just to create the man pages.
    The man pages are no longer automatically created in the build
    The man/ directory has been removed.  The man page templates
    have been moved to data/.
    New unexported module:  Text.Pandoc.ManPages.
    Text.Pandoc.Data now exports readmeFile, and `readDataFile`
    knows how to find README.
    Closes #2190.
Commits on May 29, 2015
  1. Updated INSTALL.

Commits on May 28, 2015
Commits on Apr 3, 2015
  1. Improved INSTALL instructions.

  2. Added INSTALL instructions about older cabal versions.

    IT may be necessary to update cabal, since older versions
    don't take into account the (new) possibility of changed
    metadata on Hackage.
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 Aug 31, 2013
Commits on Aug 8, 2013
  1. Improved INSTALL instructions.

Commits on Jul 26, 2012
Commits on Apr 27, 2012
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.