Re: [Xen-devel] [PATCH DOCDAY] use lynx to produce better formatted text documentation from markdown

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Matt Wilson writes ("Re: [Xen-devel] [PATCH DOCDAY] use lynx to produce better 
formatted text documentation from markdown"):
> I'm certainly not suggesting that we add a web browser to the build
> dependencies. If lynx isn't installed, the current behavior of copying
> the markdown file is maintained.
> 
> If a packager wishes to produce prettier text documentation, they can
> elect to add lynx to their build dependencies. Today doing this
> post-build from build control files is a bit tricky, since we drop the
> semantic information conveyed by the .markdown suffix by calling the
> final file .txt.
> 
> 4.2 will be the first release with markdown documentation. I think
> that making it well formatted, just as the previous .txt
> documentation, will be a better experience for the user.

I tend to agree with this line of argument.  But I have orthogonal
queries:

Firstly, why lynx and not w3m ?  Is lynx even maintained upstream any
more ?  Secondly, shouldn't we do the testing for the presence of
markdown and the html formatter in configure ?

Ian.

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