unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Eric Bavier <ericbavier@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Move cursynth to music.scm
Date: Mon, 28 Dec 2015 23:32:37 -0500	[thread overview]
Message-ID: <20151229043237.GB2878@jasmine> (raw)
In-Reply-To: <20151228171715.5450cca0@openmailbox.org>

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.

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?

> 
> > Leo Famulari (1):
> >   gnu: Move cursynth to (gnu packages music).
> > 
> >  gnu-system.am             |  1 -
> >  gnu/packages/cursynth.scm | 53 -----------------------------------------------
> >  gnu/packages/music.scm    | 27 ++++++++++++++++++++++++
> >  3 files changed, 27 insertions(+), 54 deletions(-)
> >  delete mode 100644 gnu/packages/cursynth.scm
> > 
> 

  reply	other threads:[~2015-12-29  4:32 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 [this message]
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
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=20151229043237.GB2878@jasmine \
    --to=leo@famulari.name \
    --cc=ericbavier@openmailbox.org \
    --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 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).