IRC channel logs
2025-05-24.log
back to list of logs
<pinoaffe>daviid: oh nice, thanks for the answers! <ArneBab>old: good question … maybe because debian does not differentiate between "Guile Scheme development" and "embedding Guile"? <rlb>old: I suspect that was (I?) decided that a long time ago, but it could be changed -- I haven't used guild much myself, what would we want, and what does it require (i.e. does it need other things from guile-3.0-dev?) <old>rlb: guild is a Guile script AFAIK <old>So really, it should just be in bin along guile <old>It would be nice if we could have that. Right now, I have to pull guile-3.0-dev for my CI. Which takes 5 minutes of pulling C stuffs <rlb>yes, but doesn't it depend on scripts that are also in guild-dev? <rlb>hmm, and how big is guile-3.0-dev? <rlb>It's 150k for current 3.0, so maybe that's not the main culprit? <rlb>"also in guile-3.0-dev" <old>rlb: what's huge to pull I think is all the C toolchain <old>I'll have to check the output again, but AFAIK, C stuffs were getting pulled <rlb>OK, well the issue is whether or not guild needs all of that for some of its subcommands -- if so, we can't (trivially) just move it to guile-3.0. <rlb>Not sure either way offhand. <mwette>rlb: guild needs the modules/script files; I guess it does not need more, but not certain <sneek>Welcome back mwette, you have 1 message! <sneek>mwette, wingo says: thanks, and apologies for the buggy spam filter :/ <rlb>mwette, old: ok, well I'm not opposed to rearranging the packages in forky, *if* we can determine the relevant interdependencies, and intent regarding guild there -- i.e. does guile intend to preserve the boundaries the rearrangement would depend on. <lxsameer>is guile hardwired to use glibc on linux? <Arsen>it can't decide what the compiler considers libc, so not to my awareness <lxsameer>that's what I thought, but for some reason, on a musl based system, it still look for glibc <lxsameer>probably something is wrong on my side then <lxsameer>it fails at make -C libguile scmconfig.h <Arsen> 21:23:50 <lxsameer> that's what I thought, but for some reason, on a musl based system, it still look for glibc <Arsen>because the latter is expected <Arsen>post the configure output that is concerning to you