From: Nils Gillmann <ng0@n0.is>
To: Chris Marusich <cmmarusich@gmail.com>, guix-devel@gnu.org
Subject: Re: a GUIX_PACKAGE_PATH / modules puzzle
Date: Thu, 10 May 2018 22:27:26 +0000 [thread overview]
Message-ID: <20180510222726.46zv7dsm32ufgyhj@abyayala> (raw)
In-Reply-To: <20180503083033.457tdfmh5qmauqb4@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1118 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-05-10 22:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 22:39 a GUIX_PACKAGE_PATH / modules puzzle Nils Gillmann
2018-05-03 5:16 ` Chris Marusich
2018-05-03 5:36 ` Nils Gillmann
2018-05-03 7:23 ` Chris Marusich
2018-05-03 8:30 ` Nils Gillmann
2018-05-10 22:27 ` Nils Gillmann [this message]
2018-05-10 23:26 ` Nils Gillmann
2018-05-11 7:00 ` Nils Gillmann
2018-05-11 7:19 ` Nils Gillmann
2018-05-12 13:43 ` Ricardo Wurmus
2018-05-12 19:45 ` Nils Gillmann
2018-05-13 5:15 ` Ricardo Wurmus
2018-05-11 7:36 ` Nils Gillmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180510222726.46zv7dsm32ufgyhj@abyayala \
--to=ng0@n0.is \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.