unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: beets: Update to 1.3.19.
Date: Mon, 8 Aug 2016 22:48:49 -0400	[thread overview]
Message-ID: <20160809024849.GA6974@jasmine> (raw)
In-Reply-To: <1470686133.886135.689514601.1897789E@webmail.messagingengine.com>

On Mon, Aug 08, 2016 at 02:55:33PM -0500, Alex Griffin wrote:
> Thanks for the feedback Leo!
> 
> On Sat, Aug 6, 2016, at 09:39 PM, Leo Famulari wrote:
> > Do you know how it works for Beets on "traditional" distros?
> 
> In Debian, some plugins' dependencies are optional, and the user has to
> install them explicitly. That's sort of what we're doing, except Guix
> doesn't have optional dependencies so you can't look at the package
> metadata to figure out what to install.
> 
> I don't think this approach works with python dependencies though,
> because you'll need to mess with the package description to get those
> working. If someone wanted to use the replaygain plugin with the
> gstreamer backend instead, for example, they couldn't just install
> python-gst.
> 
> I have one more patch coming to enable the acoustic fingerprinting
> plugin, then all the plugins I use will work. I think I'm just going to
> hard-code its dependencies for now, but we may need to use another
> approach if anyone wants to enable a bunch of other plugins.

Thanks for the explanation. I guess we will decide what to do when we
need to make a decision :)

      reply	other threads:[~2016-08-09  2:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 22:39 [PATCH] gnu: beets: Update to 1.3.19 Alex Griffin
2016-07-29 23:24 ` Leo Famulari
2016-08-03 22:38   ` Alex Griffin
2016-08-07  2:39     ` Leo Famulari
2016-08-08 19:55       ` Alex Griffin
2016-08-09  2:48         ` Leo Famulari [this message]

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=20160809024849.GA6974@jasmine \
    --to=leo@famulari.name \
    --cc=a@ajgrf.com \
    --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).