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

[Matt Wilson <msw@xxxxxxxxxx>]

On Thu, Aug 30, 2012 at 04:41:08PM +0100, 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.

For what it's worth, if ./configure is run and a markdown binary is
found in $PATH, $(MARKDOWN) will be the full path detected at
./configure time like /usr/bin/markdown and the "which" bit will be a
no-op.

> Keir, would it be OK if we simply declared that you must run configure
> to "make docs" ?
> 
> Ian.

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