From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nils Gillmann Subject: Re: a GUIX_PACKAGE_PATH / modules puzzle Date: Fri, 11 May 2018 07:00:50 +0000 Message-ID: <20180511070050.oijp5l6mm5smtvuk@abyayala> References: <20180501223951.whoj67yv2h3t6wyl@abyayala> <87bmdxwc6y.fsf@gmail.com> <20180503053613.dffmd6ag57x26fdt@abyayala> <87a7thxkw2.fsf@gmail.com> <20180503083033.457tdfmh5qmauqb4@abyayala> <20180510222726.46zv7dsm32ufgyhj@abyayala> <20180510232635.ncez2ai4736cysfd@abyayala> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49348) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fH22X-0007I4-Gf for guix-devel@gnu.org; Fri, 11 May 2018 03:00:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fH22T-0001eK-GX for guix-devel@gnu.org; Fri, 11 May 2018 03:00:29 -0400 Received: from conspiracy.of.n0.is ([2a01:4f8:1c0c:7ad0::1]:34414) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fH22T-0001cW-6f for guix-devel@gnu.org; Fri, 11 May 2018 03:00:25 -0400 Received: by conspiracy.of.n0.is (OpenSMTPD) with ESMTPSA id f4d510ad (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO) for ; Fri, 11 May 2018 07:00:21 +0000 (UTC) Content-Disposition: inline In-Reply-To: <20180510232635.ncez2ai4736cysfd@abyayala> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org 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 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. >