[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 2 of 3] docs: use elinks to format markdown-generated html to text


  • To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Matt Wilson <msw@xxxxxxxxxx>
  • From: Keir Fraser <keir.xen@xxxxxxxxx>
  • Date: Thu, 30 Aug 2012 16:47:29 +0100
  • Cc: xen-devel@xxxxxxxxxxxxx
  • Delivery-date: Thu, 30 Aug 2012 15:48:09 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac2GxsKXucl+HdXqDke168ZmujqKyQ==
  • Thread-topic: [Xen-devel] [PATCH 2 of 3] docs: use elinks to format markdown-generated html to text

On 30/08/2012 16:41, "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx> 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.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.