Re: Testing unusual build options

2017-02-02 Thread Sanjeev Gupta
On Fri, Feb 3, 2017 at 5:12 AM, Gary E. Miller wrote: > I would want my installedcode to match my installed doc. If you are editing only the docs (as I do), you may wish to rebuild the docs after every commit to check. Since waf is so fast, I just do a ./waf build anyway, so this is academic f

Re: Testing unusual build options

2017-02-02 Thread Eric S. Raymond
Hal Murray : > > e...@thyrsus.com said: > > That soumds like a request for two two different *install* productions. > > Noted. > > I could easily imagine a rats-nest. True, but that's orthogonal to whether it's a rat's nest at choice-of-config time or a rat's nest at choice-of-install time. >

Re: Testing unusual build options

2017-02-02 Thread Hal Murray
e...@thyrsus.com said: > That soumds like a request for two two different *install* productions. > Noted. I could easily imagine a rats-nest. Why just two? How about a no-ntpviz option? How about a no-clients option? The latter gets "interesting". I think there are two types of clients. T

Re: Testing unusual build options

2017-02-02 Thread Eric S. Raymond
Hal Murray : > > >> --enable-doc-only doesn't build any documentation. :) > > I think that is a silly option, and a perfect example of how the recipe got > > overcomplicated. I'm going to remove it. > > How do I update the installed documentation without updating the code? That soumds like a

Re: Testing unusual build options

2017-02-02 Thread Hal Murray
> I would want my installedcode to match my installed doc. I agree. But use your imagination. The default is no doc. You have to turn on --enable-doc to get it. Suppose I have done extensive testing with the installed code but forgot to turn on --enable-doc. Why should I re-install the same

Re: Testing unusual build options

2017-02-02 Thread Gary E. Miller
Yo Hal! On Thu, 02 Feb 2017 13:03:24 -0800 Hal Murray wrote: > >> --enable-doc-only doesn't build any documentation. :) > > I think that is a silly option, and a perfect example of how the > > recipe got overcomplicated. I'm going to remove it. > > How do I update the installed documenta

Re: Testing unusual build options

2017-02-02 Thread Hal Murray
>> --enable-doc-only doesn't build any documentation. :) > I think that is a silly option, and a perfect example of how the recipe got > overcomplicated. I'm going to remove it. How do I update the installed documentation without updating the code? -- These are my opinions. I hate spam.

Re: Testing unusual build options

2017-02-02 Thread Eric S. Raymond
Hal Murray : > --enable-doc-only doesn't build any documentation. :) I think that is a silly option, and a perfect example of how the recipe got overcomplicated. I'm going to remove it. -- http://www.catb.org/~esr/";>Eric S. Raymond __

Re: ntpq peers formatting needs floating point for time slots.

2017-02-02 Thread Eric S. Raymond
Hal Murray : > > e...@thyrsus.com said: > >> Looks like lines from ntpmon are one character shorter than ntpq. > > They use the same display code - pylib/uril.py::PeerSummary. > > I get the same width when run directly on a system, but see the difference > when ssh-ing into that system. > > Th

Re: ntpq peers formatting needs floating point for time slots.

2017-02-02 Thread Hal Murray
e...@thyrsus.com said: >> Looks like lines from ntpmon are one character shorter than ntpq. > They use the same display code - pylib/uril.py::PeerSummary. I get the same width when run directly on a system, but see the difference when ssh-ing into that system. The refid column and everything t

Re: ntpq peers formatting needs floating point for time slots.

2017-02-02 Thread Eric S. Raymond
Hal Murray : > Right now, I've got a ntpmon window with 5 servers and 4 blank lines after > the lines that exactly fill the whole line. Have you tried adjusting your > window for an exact fit? I have. I did that when testing my change. > Looks like lines from ntpmon are one character shorter

Re: ntpq peers formatting needs floating point for time slots.

2017-02-02 Thread Hal Murray
e...@thyrsus.com said: >> The current display is 78 characters wide. Is there a good reason >> not to use the last 2? > Nope. That's what my previous commit did. There may be quirks with somebody putting in a line break at exactly 80 rather than waiting to see if the next character is a retu

Re: ntpq peers formatting needs floating point for time slots.

2017-02-02 Thread Eric S. Raymond
Hal Murray : > The current display is 78 characters wide. Is there a good reason not to use > the last 2? Nope. That's what my previous commit did. -- http://www.catb.org/~esr/";>Eric S. Raymond ___ devel mailing list devel@ntpsec.org

Testing unusual build options

2017-02-02 Thread Hal Murray
At Gary's suggestion a while ago, I just pushed a script that will test various configuration combinations. Partly, I was trying to make sure all of the options were tested. It's tests/option-tester.sh It writes stuff into ./test-xxx where xxx is the tag for an individual test. If you have an

Re: ntpq peers formatting needs floating point for time slots.

2017-02-02 Thread Hal Murray
e...@thyrsus.com said: > Sigh. I'll revert that commit. I don't think there's any horizontal slack > left in the display, then. Don't revert. I'll fix it. The current display is 78 characters wide. Is there a good reason not to use the last 2? g...@rellim.com said: > Hal already updated y