On Tue, Sep 16 2025, jakeleporte wrote: > Still can't seem to get Lua packages working right- adding them to the > profile doesn't result in Prosody seeing them, but for now I'm using > input rewriting to add them as inputs to my Prosody package, [...]
As you mentioned in your earlier email, Lua search paths are not handled well in Guix[1]. Prosody's build explicitly constructs LUA_PATH and LUA_CPATH from the inputs to the package, so your workaround makes sense. I spent some time looking into it last night and have raised a PR in Codeberg with a potential improvement[2], but I don't think it will fix your problem because the Prosody service does not construct a profile. What you're doing seems reasonable. PostgreSQL does something similar by creating a postgresql package that is just the union of postgresql and all of the extensions you request. Perhaps the Prosody service should do something to explicitly pull in the plugins and their dependencies. Carlo [1]: https://issues.guix.gnu.org/issue/25425 [2]: https://codeberg.org/guix/guix/pulls/2743
