public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Dev version and latest binary at the same time
Date: Mon, 14 Sep 2020 11:02:19 +0200	[thread overview]
Message-ID: <87r1r4n338.fsf@zeitkraut.de> (raw)
In-Reply-To: <80c2e758-19f5-cb58-a4df-9b2df8a66b50-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>


Denis Maier writes:

> is there a recommended way for having the dev version and the latest official
> version installed at the same time? How can you still use the official version
> in a production environment while tinkering with the dev version?

I'm using Docker to fix specific versions. We provide images for pandoc
2.6 and later (although I recently realized that we haven't published
2.10.1 yet). I rely heavily on Makefiles and put the path to pandoc in a
variable:

    PANDOC_VERSION ?= 2.7.3
    PANDOC ?= docker run --rm -it -v $(PWD):/data -u $(id -u):$(id -g) pandoc/latex:$(PANDOC_VERSION)

    %.pdf: %.md
      $(PANDOC) --output=$@ $<

Then I can run

    make my-doc.pdf

for a normal build,

    make my-doc.pdf PANDOC_VERSION=2.9.2.1

to use a different published version, or

    make my-doc.pdf PANDOC=local/dev/pandoc

to use a local version.



--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


  parent reply	other threads:[~2020-09-14  9:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  8:10 Denis Maier
     [not found] ` <80c2e758-19f5-cb58-a4df-9b2df8a66b50-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-14  9:02   ` Albert Krewinkel [this message]
     [not found]     ` <87r1r4n338.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-09-14 19:48       ` Denis Maier
2020-09-14 16:23   ` John MacFarlane
     [not found]     ` <m2imcgnx8e.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-14 19:46       ` Denis Maier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1r4n338.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).