From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Trouble with circular module dependencies (Re: 01/02: gnu: Add ncurses-with-gpm.)
Date: Thu, 27 Jul 2017 11:01:20 +0200 [thread overview]
Message-ID: <87eft26yov.fsf@gnu.org> (raw)
In-Reply-To: <87d18o6wah.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 25 Jul 2017 23:28:38 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> skribis:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> FWIW, I would like to see us work to eliminate all cyclic module
>>> dependencies in Guix, by splitting up our package modules as needed so
>>> that they form a directed acyclic graph.
>>
>> This seems hard to achieve, unless we use one file per package.
>
> Are there drawbacks to using one file per package other than it’s a bit
> “heavy” due to all the boilerplate of license headers and module
> definitions?
It’d be less convenient for packagers, notably because you’d have to
specify all the modules to import, as you noted before. We could work
around it with a ‘define-package-module’ macro that would lookup
packages with ‘specification->package’ or something like that.
There might be other implications, I’m not sure.
Ludo’.
next prev parent reply other threads:[~2017-07-27 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170715081544.12288.82778@vcs0.savannah.gnu.org>
[not found] ` <20170715081545.DB2A022E4F@vcs0.savannah.gnu.org>
2017-07-23 22:22 ` Trouble with circular module dependencies (Re: 01/02: gnu: Add ncurses-with-gpm.) Mark H Weaver
2017-07-24 6:37 ` Ricardo Wurmus
2017-07-24 9:25 ` Ludovic Courtès
2017-07-25 21:28 ` Ricardo Wurmus
2017-07-25 21:45 ` Danny Milosavljevic
2017-07-26 7:30 ` Alex Sassmannshausen
2017-07-27 9:01 ` Ludovic Courtès [this message]
2017-07-25 21:59 ` Danny Milosavljevic
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eft26yov.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).