Re: Including SRFI-197

2025-06-18 Thread Maxim Cournoyer
Hi, Rob Browning writes: [...] > I went ahead and moved SRFI-197 to the newer commit so we have the new > SPDX headers, but I also kept the license text in each file for now > under the assumption that I should stick to the current convention > until/unless Guile itself adopts SPDX. I think th

Re: Including SRFI-197

2025-06-18 Thread Maxim Cournoyer
Hi Rob, Rob Browning writes: > Rob Browning writes: > >> So for now I've attempted to just allow us to mix and match SRFI-64 and >> (test-suite lib) based tests by integrating SRFI-64 into the existing >> automake/check-guile arrangement via a suitable test driver. > > I've pushed this prelimin

Re: Including SRFI-197

2025-06-18 Thread Rob Browning
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

Re: Including SRFI-197

2025-06-18 Thread Tomas Volf
Maxim Cournoyer writes: > Hi Rob, > > Rob Browning writes: > >> Rob Browning writes: >> >>> So for now I've attempted to just allow us to mix and match SRFI-64 and >>> (test-suite lib) based tests by integrating SRFI-64 into the existing >>> automake/check-guile arrangement via a suitable test