Are there any plans to use autoconf to build MaraDNS?
No. In more detail, MaraDNS does not use autoconf for the following reasons: • Autoconf is designed to solve a problem that existed in the mid 1990s but does not exist today: A large number of different incompatible C compilers and libc implementations. These days, most systems are using gcc as the compiler and some version of glibc as the libc. There is no longer a need, for example, to figure out whether a given implementation of getopt() allows ‘–‘ options. MaraDNS’s ./configure script can be run in only a second or two; compare this to the 3-5 minute process autoconf’s ./configure needs. • Autoconf leaves GPL-tained files in a program’s build tree. MaraDNS is licensed under a BSD license that is not GPL-compatible, so MaraDNS can not be distributed with these GPL-licensed files.
