From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Move cursynth to music.scm
Date: Wed, 30 Dec 2015 00:33:25 +0100 [thread overview]
Message-ID: <877fjwzv7e.fsf@gnu.org> (raw)
In-Reply-To: <87k2nx4tq6.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 29 Dec 2015 08:08:49 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Leo Famulari <leo@famulari.name> writes:
>
>> On Mon, Dec 28, 2015 at 05:17:15PM -0600, Eric Bavier wrote:
>>> On Mon, 28 Dec 2015 18:09:09 -0500
>>> Leo Famulari <leo@famulari.name> wrote:
>>>
>>> > I think it would be better for this software synthesizer to be in
>>> > music.scm.
>>> >
>>> > Thoughts?
>>>
>>> IIRC, the original thought was that many GNU packages have their own
>>> modules, so this was done for cursynth as well.
>>
>> Okay, sure.
>
> I think it would be nice to have cursynth in “music.scm”.
+1
>> To be honest, I don't understand the reasoning behind grouping packages
>> into modules. Is it just for humans or is there some technical reason
>> for it?
>
> It’s mostly for humans AFAIU. Personally, I prefer try to avoid a
> proliferation of one-off modules; maybe because I don’t like the
> boilerplate (license header, module definition with imports, adding the
> module to “gnu-system.am”).
Same here.
More modules also lead to more I/O for the various commands.
Ludo’.
next prev parent reply other threads:[~2015-12-29 23:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 23:09 [PATCH 0/1] Move cursynth to music.scm Leo Famulari
2015-12-28 23:09 ` [PATCH 1/1] gnu: Move cursynth to (gnu packages music) Leo Famulari
2015-12-28 23:17 ` [PATCH 0/1] Move cursynth to music.scm Eric Bavier
2015-12-29 4:32 ` Leo Famulari
2015-12-29 7:08 ` Ricardo Wurmus
2015-12-29 9:14 ` Alex Kost
2015-12-29 10:50 ` Leo Famulari
2015-12-29 23:33 ` Ludovic Courtès [this message]
2015-12-30 1:10 ` Leo Famulari
2015-12-31 2:31 ` Leo Famulari
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=877fjwzv7e.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).