From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: [PATCH 0/1] Move cursynth to music.scm Date: Tue, 29 Dec 2015 08:08:49 +0100 Message-ID: <87k2nx4tq6.fsf@elephly.net> References: <20151228171715.5450cca0@openmailbox.org> <20151229043237.GB2878@jasmine> 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]:44964) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDoOx-0003wx-QQ for guix-devel@gnu.org; Tue, 29 Dec 2015 02:09:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aDoOu-0006JO-JS for guix-devel@gnu.org; Tue, 29 Dec 2015 02:08:59 -0500 Received: from sender163-mail.zoho.com ([74.201.84.163]:25928) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDoOu-0006J4-Bi for guix-devel@gnu.org; Tue, 29 Dec 2015 02:08:56 -0500 In-reply-to: <20151229043237.GB2878@jasmine> 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: Leo Famulari Cc: guix-devel@gnu.org 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”. I wasn’t fully aware of its existence, and I’m at home in “audio.scm” and “music.scm” :) > 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”). Grouping packages in modules also allows user interfaces like guix-web to narrow results to just a single module. For example, searching for “bioinfo” in guix-web shows me everything from the “bioinformatics.scm” module, even though not all packages there contain the string “bioinfo” in their synopsis/description. ~~ Ricardo