path: root/
diff options
authorJohn MacFarlane <>2017-02-20 21:07:59 +0100
committerJohn MacFarlane <>2017-02-20 21:07:59 +0100
commit3c8ccd2a9c67793f182179e7c5a221841ee2b6e2 (patch)
treef1f870951b15b7796f3f1a052f3218f772eec0c4 /
parente390d754ef762d85db53a1e1ad978d16c30d68f7 (diff)
Modified documentation now that submodule fetching isn't needed.
Diffstat (limited to '')
1 files changed, 2 insertions, 11 deletions
diff --git a/ b/
index 4f833b471..5918eea53 100644
--- a/
+++ b/
@@ -112,7 +112,6 @@ Or you can fetch the development code by cloning the repository:
git clone
cd pandoc
- git submodule update --init # to fetch the templates
Note: there may be times when the development code is broken
or depends on other libraries which must be installed
@@ -159,13 +158,6 @@ The easiest way to build pandoc from source is to use [stack]:
cabal install
- Note: If you obtained the source from the git repository (rather
- than a release tarball), you'll need to do
- git submodule update --init
- to fetch the contents of `data/templates` before `cabal install`.
4. Make sure the `$CABALDIR/bin` directory is in your path. You should
now be able to run `pandoc`:
@@ -329,14 +321,13 @@ maximal build method would be
git clone
git clone
cd pandoc
- git submodule update --init
stack install --test --install-ghc --stack-yaml stack.full.yaml
To pull in the latest changes, after you've done this and there have been
changes in the repositories: Visit each repository in pandoc-build
(pandoc-types, texmath, pandoc-citeproc, pandoc, zip-archive, cmark-hs) and do
-`git pull`. In the pandoc repo, also do `git submodule update` and `stack
-install --test --stack-yaml stack.full.yaml`.
+`git pull`. In the pandoc repo, also do `stack install --test
+--stack-yaml stack.full.yaml`.