From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH 2 of 3] docs: use elinks to format markdown-generated html to text Date: Thu, 30 Aug 2012 16:47:29 +0100 Message-ID: References: <20543.35220.572436.112964@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20543.35220.572436.112964@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson , Matt Wilson Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 30/08/2012 16:41, "Ian Jackson" wrote: > Matt Wilson writes ("[Xen-devel] [PATCH 2 of 3] docs: use elinks to format > markdown-generated html to text"): >> Markdown, while easy to read and write, isn't the most consumable >> format for users reading documentation on a terminal. This patch uses >> lynx to format markdown produced HTML into text files. > ... >> txt/%.txt: %.markdown >> - $(INSTALL_DIR) $(@D) >> - cp $< $@.tmp >> - $(call move-if-changed,$@.tmp,$@) >> + @$(INSTALL_DIR) $(@D) >> + set -e ; \ >> + if which $(MARKDOWN) >/dev/null 2>&1 && \ >> + which $(HTMLDUMP) >/dev/null 2>&1 ; then \ >> + echo "Running markdown to generate $*.txt ... "; \ > > So now we have two efforts to try to find markdown, one in configure > and one here. > > Keir, would it be OK if we simply declared that you must run configure > to "make docs" ? Yes! -- Keir > Ian.