Tomas Volf <~@wolfsden.cz> writes: > I would assume the reason here is Automake.
Exactly, we need some way to know which test harness we're using for each file, (test-suite lib) or (srfi srfi-64), and with the current arrangement, that ends up in in ./check.guile.in where we decide whether to run guile-test, which ends up in ((test-suite lib automake) main), or ((srfi srfi-64 automake) main), depending on the extension. This approach also preserves the ability to run either flavor directly via ./check-guile something. We actually do use the same automake DRIVER, i.e. test-suite/driver via test-suite/Makefile.am. And of course there are other approaches we can take, if/when we prefer. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
