MIME-Version: 1.0 In-Reply-To: X-Mailer: MIME-tools 5.505 (Entity 5.505) Content-Disposition: inline X-RT-Interface: Web References: Content-Type: text/plain; charset="utf-8" Message-ID: Content-Transfer-Encoding: binary X-RT-Original-Encoding: utf-8 RT-Send-CC: X-RT-Encrypt: 0 X-RT-Sign: 0 Content-Length: 1230 On Sat Apr 29 21:10:39 2017, tm_iscbind@10am.com wrote: > / [issue.1: -v output does not use STDOUT] => this comes from nslookup which originally was not an ISC program so this behavior was kept and extended to dig, host, nsupdate, etc. Only named itself is different. Two other comments: - changing this for the 12th release will break a lot of scripts - you can simply redirect the standard error to the standard output. In conclusion this issue was rejected. > / [issue.2: no windows file properties] => as you can expect bind9 is heavily Unix bound so only the pure WIN32 code got a resource file and a direct win32 directory. Only BINDInstall.exe (bin/win32) and bindevt.dll (lib/win32) have properties and BTW changed very infrequently (last important update in the BINDInstall code was to use a manifest file (vs builtin list) with the things to install in order to make the installer independent of a particular bind version). Note the information exists, for instance you have the interface/revision/age triplet for each library in the corresponding api file so you can imagine to improve the build system to generate and include resource files. (If you are interested to contribute I can send details to you).