Re: [chrony-dev] Documentation patch

2016-10-24 Thread Bill Unruh
The problem I have with asciidoctor is that it seems to be a redhat only thing, at least in rpms. One should then tell people how to get asciidoctor in case their distro does not have it, and that one has to have ruby installed in order to use it. On Mon, 24 Oct 2016, Miroslav Lichvar wrote:

Re: [chrony-dev] Documentation patch

2016-10-24 Thread Miroslav Lichvar
On Sat, Oct 22, 2016 at 05:46:53AM -0700, Bill Unruh wrote: > Probably. I am a bit confused why asciidoctor would be used instead of, the > seeming more prevalant, asciidoc, or either, set up by configure after testing > what the system has. asciidoc is an older and well-known implementation, but

Re: [chrony-dev] Documentation patch

2016-10-22 Thread Håkan Johansson
On Sat, 22 Oct 2016, Rune Magnussen wrote: På Fri, 21 Oct 2016 16:11:16 -0700 (PDT) Bill Unruh skrev: On Sat, 22 Oct 2016, Rune Magnussen wrote: Hi When trying to install chrony from source, I found out that the README refered to INSTALL which does not exist. Also

Re: [chrony-dev] Documentation patch

2016-10-21 Thread Vincent Blut
On Fri, Oct 21, 2016 at 04:35:55PM -0700, Bill Unruh wrote: On Fri, 21 Oct 2016, Bill Unruh wrote: On Sat, 22 Oct 2016, Rune Magnussen wrote: Hi When trying to install chrony from source, I found out that the README refered to INSTALL which does not exist. Also asciidoctor is needed during

Re: [chrony-dev] Documentation patch

2016-10-21 Thread Bill Unruh
On Sat, 22 Oct 2016, Rune Magnussen wrote: Hi When trying to install chrony from source, I found out that the README refered to INSTALL which does not exist. Also asciidoctor is needed during install. here is a patch to fix the docs. Not at all sure where you are getting your source for