Questions of clarification:
TBQH, I would be tempted to just do:
ls data/*.lisp | perl -ne 'chomp; print("(:file \"$_\")\n");'
In order to get a set of lines I could include in my system definition (if you hate perl, you could probably use sed and awk; I've never mastered these). I.e., what's so bad about having to list the files explicitly? One could even use a makefile to automate this process. Or, if you wanted to do this purely in CL, I suppose you could write a "meta-ASDF" operation that would generate the ASDF defsystem. That seems like way too much work, though.
On 30 Nov 2025, at 5:20, Marco Antoniotti wrote:
Hello parenthetically unchallenged friends!Suppose I have a library that is structured assrc/code.lisppkg.lispstuff.lispdata/data-file-1.lispdata-file-2.lispdata-file-3.lisp...data-file-3-point-14-godzillion.lispActually, the data folder could be anywhere.How do I tell ASDF (or similar) to just slurp in all the data files at once? I know it's doable, but maybe someone knows of a better way.ThanksMarco--
Marco Antoniotti, Professor, Director tel. +39 - 02 64 48 79 01REGAINS: https://regains.disco.unimib.it/
DISCo, University of Milan-Bicocca U14 2043 http://dcb.disco.unimib.it
Viale Sarca 336
I-20126 Milan (MI) ITALY