Metaconf uses the concept of "Unit" files (similar to an autoconf macro).

When designing a package that uses metaconf, one just lists the "pieces" one
needs, and the generator takes these things and (using "make -n", as I
recall), finds all of the prerequisites, orders the tests, anad produces a
Configure script.

Unit files are nice because we could very easily include lots of them
(including some obscure ones) as well as different ways to do the same thing
in the metaconf distribution (Larry used one style of Endian testing and I
used a different one; both styles are/were in the distribution).

H

Reply via email to