IRC channel logs
2026-08-16.log
back to list of logs
<loon>trying to run `gnulib-tool --add-import glob` and I'm getting a license conflict error because glob (and several dependencies) are GPL rather than, I'm guessing, LGPL. how do I proceed in this case? <loon>(... beginning to wonder if this is why guile doesn't have bindings for glob(3)) <loon>I'm fine with adding a check in configure.in etc. and using the host's libc's glob(3) if it has one, but would like suggestions on any better ideas folks have <rlb>Hmm, interesting, didn't recall the possibility of gnulib license conflicts. And yeah, I'd assume that's the likely alternative --- just rely on the host. If it looks like it's going to be a lot of work, might want to see what Olivier thinks first. <old>ArneBab: BLUE is not guile specific. It's a general purpose build system framework <old>But indeed you could call it from make <old>and generate the rules from that <ArneBab>old: in a $(guile …) rule? (does it provide imports for that) <rlb>Olivier -- btw, I'd also augmented pass-if-exception and expect-fail-exception to accept a procedure/predicate in utf8 (instead of the pair), so you can do whatever you want to validate the exception, but that should be orthogonal to your exception-with-message change (rebasing now). <rlb>I could pull that forward if we had any interest, but there's no need for it until later in utf8. <rlb>(had also fixed up the docs, and will plan to add the exception-with-message support later too) <rlb>I also vaguely wonder if we might want to just lean on that procedure option (with helpers) instead of adding more fixed-pattern special cases. i.e. (pass-if-exception ... (ex-with-message-matching "some pattern") ...) where ex-with-message-matching returns a suitable predicate. <JohnCowan>implementing wordexp with a shell soundst to me like a terrible approach: too heavyweight and exposes sh bugs to random applications, not to mention the issue of where a posix shell might be (/bin/dash, /bin/ash, somewhere else, nowhere?) <rlb>I don't disagree in general, and I'd forgotten that /bin/sh isn't one of the (very) few required posix paths. I vaguely recall there being some.