> Is it really desirable to have complex build tools be part of the project, especially after the xz-utils takeover? That's a fair question, but i'm confident

> Is it really desirable to have complex build tools be part of the project, especially after the xz-utils takeover? That's a fair question, but i'm confident that in this case such a risk is simply not there. We've interacted with the maintainer of Autosetup and JimTCL (the same guy) for more than a decade and know he runs a proverbial "tight ship." Autosetup has two major components: - TCL-based scripts to process configure-style scripts and work with file templates in a way nearly identical to autotools (e.g. Makefile.in uses the same syntax). - JimTCL is a TCL implementation which lives in the tree, allowing folks who won't have the canonical TCL installed to run the build. Steve Bennett maintains both of those and is extremely conscientious about what goes into his trees. Over the years, as we've updated our in-tree copy in the Fossil SCM, it's become habit to peruse the diffs of the upgraded files, comparing them to our previous install. In the unlikely case that someone were to sneak some mischief in, i'm fairly confident that we would catch it, at the latest, at that point (before checking in that change to our project).