The method is strange and has unexpected dependencies. Putting the
responsibility to prepare tfkit to Makefile author's hands seems
cleaner--they need to set TF_DIR properly so it's sort of intuitive;
also it allows them to choose way how to deploy tfkit itself (sub-repo,
submodule, or hard copy).
Make it
* more flexible,
* more readable,
* faster,
* take care of manpages (not fully done yet),
* take care of dist list,
* little bit more polished in various other things.
As a followup to last revamp:
* Use more extensible test definition format,
* separate testing framework from setup script and split to includes,
* update test scripts as well as data,
* consolidate test output,
* and make some small improvements/fixes on the way.
* Enable running all tests via make,
* simplify tests (lay off data/tmpdir manipulation to framework),
* set rules for naming, exit statuses, etc,
* remove beakerlib dependency.
Add ability to include code examples from "real" files
Now we can keep examples as a "real" shell scripts, taking advantage
of ability to test them or edit them with proper syntax HL.
Setup will now automatically insert them and indent properly as code.
Small drawback is that we cannot build manpages separately, but since
all building is to be trivial this is not a big deal.