Hi pinoaffe,
Il 29/07/26 08:59, pinoaffe ha scritto:
Simon Tournier <[email protected]> writes:
On Sat, 20 Jun 2026 at 00:20, Tomas Volf <[email protected]> wrote:
The name change seems like a wise idea. It would be somewhat
frustrating for `guix' command to behave differently based on whether
this hypothetical guile-guix-records is installed in my home profile.
No worry, because I don’t think it’s possible since the Guile module
paths are hard-coded inside the Guix bash wrapper.
Couldnt this still cause issues if, in a guile repl, I import guix?
I think it could, or that in general it's too much of a risk that a
simple rename can avoid. I renamed the module to (guix-lib guix records)
[0]. The idea is that the (guix-lib ...) namespace could contain more of
Guix internals that could be depended upon independently. They could
also be stored in a (separate) monorepo I believe and built as separate
packages from there.
I have been testing (guix-lib guix records) for a couple of months and I
have not yet found unexpected behavior. I think if the community likes
this approach it can be applied to other Guix modules.
Cheers,
giacomo
[0]:
https://codeberg.org/fishinthecalculator/guix-records/commit/e77ee9c89f34cae0b19f929f926758ce046186a3
