Re: Documentation for waf options

2018-03-12 Thread Hal Murray via devel
> Where do you want to document it? Is "./waf configure --help" sufficient? I don't have a good suggestion. It's the sort of detail that belongs in an overview section, but nobody ever reads those. Do we have an overview section? > (packaging/packaging.txt has several typos related to --build

Re: Documentation for waf options

2018-03-12 Thread Matthew Selsky via devel
On Mon, Mar 12, 2018 at 06:05:34PM -0700, Hal Murray wrote: > I don't know of any place that says anything about which form does/doesn't > work. > > What should our documentation say or examples use? Where do you want to document it? Is "./waf configure --help" sufficient? (packaging/packagin

Re: Documentation for waf options

2018-03-12 Thread Hal Murray via devel
>> How am I supposed to figure out that the format is >> --build-epoch=$date >> rather than >> --build-epoch $date > Both forms work. Thanks. > Do we suggest that only 1 form works somewhere? ./waf configure --help shows the = version I don't know of any place that says anything about which

Re: Documentation for waf options

2018-03-12 Thread Matthew Selsky via devel
On Sat, Mar 10, 2018 at 02:49:06PM -0800, Hal Murray via devel wrote: > > How am I supposed to figure out that the format is > --build-epoch=$date > rather than > --build-epoch $date > > None of the examples show the equal sign. Hey Hal, Both forms work. Do we suggest that only 1 form work

Documentation for waf options

2018-03-10 Thread Hal Murray via devel
How am I supposed to figure out that the format is --build-epoch=$date rather than --build-epoch $date None of the examples show the equal sign. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpse