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 __