Danny Milosavljevic

The point is that the "depth of cairo" loaded another version of glib. So that's where another version of glib comes from. I'm trying `test/insanity.scm` now--I only now saw the...

I agree. But what guix's gobject-introspection does is a wrong thing in general, and *libcairo-gobject is being loaded by guile-gi right now* (note: I did not directly use cairo anywhere)....

Ohhh, libguile-gi links to libgobject at compile time, too. Well, that's gonna be a problem if that library is different to the one dlopen'ed...

>I highly doubt you'll find a fix to this in Guix. Right now I'll settle for a procedure to flag this problem in Guix--nevermind fixing it. >A patch to dynamically...

ldd shows what would be loaded when loading this `so`. It can only show things that are known without actually executing user code of that `so`. That means it shows...

In the end this is the usual recursive definition problem. I don't get why people always do that--that *has* to lead to problems sooner or later. For example having a...

>Philosophically speaking, it wouldn't be much of an introspection if one was doing it from the outside, would it? It's doing it from the outside anyway because C has no...

I think it wouldn't help. If you did do it (and also did it in gobject-introspection), care would have to be taken not to pass any gobject-introspection-internal things (like GITypeInfo)...

Yeah, this is the main thing Guix is known for: reproducible builds. Full disclosure: I've been using Guix since 2017, and am working on GNU Mes for Guix for several...

Hmm, if we only want to use guix for the toolchain, that could be accomplished by building Heads or Linux or whatever with (working directory is your source code): `guix...