Re: a GUIX_PACKAGE_PATH / modules puzzle

[Nils Gillmann]

Nils Gillmann transcribed 1.9K bytes:
> Nils Gillmann transcribed 1.4K bytes:
> > Nils Gillmann transcribed 2.1K bytes:
> > > Okay, here's what I learned:
> > > 
> > > * except for source code, the modules itself in Guile aren't very
> > > * detailed documented. The documentation is good, but...  ... it's
> > > * nowhere mentioned that you can have a module (foo bar baz) and
> > > * possibly also (foo bar baz kim) but (foo baz bar bar) will lead to
> > > * the error I described.
> > > 
> > > So until I read into the core of Guile, I have 2 questions:
> > > 
> > > 1. Is there a module name maximum length? -> So far I have encountered
> > > very short module names in the wild, 3 the longest.
> > > 
> > > 2. Is this really a module length problem? -> I have a functional set
> > > of packages elsewhere, my non-core packages, named like (ports editors
> > > foo foo) and so forth and they cause no problems. It's just weird to
> > > me that the modules in ports and elsewhere work but in pkgs I can't
> > > dissect the exact problem so far. I'm okay with any namespace, so
> > > I'll simply remove the last element of the module names.
> > > 
> > > I'd like to improve documentations or other relevant places if
> > > what I experienced is some kind of corner case in module naming,
> > > be it in Guix or Guile... or just to note what to avoid with
> > > regards to modules.
> > 
> > 
> > Actually the problem is not really module names I just found out.
> 
> Here's what's happening now:
> 
> I took my perl module which is in "pkgs/lang-perl/perl.scm", which contains 
> our basic perl packages,
> and moved ( + renamed ) them into (core lang-perl perl) in a new directory.
> 
> If I run GUIX_PACKAGE_PATH="/home/user/src/core" package -s mc I get results 
> for query "mc".
> When I run GUIX_PACKAGE_PATH="/home/user/src/core" package --show=perl I get 
> the same message

Sorry, I was wrong (--show=perl works as expected).
However having the same in the old structure with just this module (and the old
name) does throw the old error. ccach of Guile is cleaned.

> as initially pointed out in the opening post.
> 
> > But I'm still curious about any possible guile module naming related limits
> > and hints from people working longer with Guile.
> > 
>