From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH 0/1] Move cursynth to music.scm Date: Tue, 29 Dec 2015 20:10:02 -0500 Message-ID: <20151230011002.GA9185@jasmine> References: <20151228171715.5450cca0@openmailbox.org> <20151229043237.GB2878@jasmine> <87k2nx4tq6.fsf@elephly.net> <877fjwzv7e.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:32944) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aE5HF-0008R2-7Q for guix-devel@gnu.org; Tue, 29 Dec 2015 20:10:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aE5HC-0004Yx-01 for guix-devel@gnu.org; Tue, 29 Dec 2015 20:10:09 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:38255) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aE5HB-0004Yh-T1 for guix-devel@gnu.org; Tue, 29 Dec 2015 20:10:05 -0500 Content-Disposition: inline In-Reply-To: <877fjwzv7e.fsf@gnu.org> 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic =?iso-8859-1?Q?Court=E8s?= Cc: guix-devel@gnu.org On Wed, Dec 30, 2015 at 12:33:25AM +0100, Ludovic Courtès wrote: > Ricardo Wurmus skribis: > > > Leo Famulari 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 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. That's a good reason. I'll apply the patch if there are no objections. > > Ludo’.