> This is trivially solved by having "install.sh"

> There are also various limitations, caveats, &c. such that I typically had a "build.sh" or some-such that did any necessary pre-tup work.

Frankly if I need to write custom wrapper scripts for a build system then the build system isn't up to scratch. On every project I work on, you can run

    make list

To get a list of targets, and build/install/predeps/deploy are all defined. On any of of our projects, make predeps && make build will output a deployable binary.

> Calculating this outside of tup is fine even if it's expensive, as long as it changes rarely.

So no include files? That's another deal-breaker!