From: Alex Griffin <a@ajgrf.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: beets: Update to 1.3.19.
Date: Wed, 03 Aug 2016 17:38:40 -0500 [thread overview]
Message-ID: <1470263920.2786216.685350833.2EB326FC@webmail.messagingengine.com> (raw)
In-Reply-To: <20160729232420.GA16663@jasmine>
On Fri, Jul 29, 2016, at 06:24 PM, Leo Famulari wrote:
> > (I'm also working on a few more patches to enable more beets plugins.
> > They'll probably be ready sometime this weekend.)
>
> Doubly awesome!
The most important plugin that I'm missing is the replaygain plugin, and
I've got it working on my system now. There are multiple replaygain
backends, and I wanted the bs1770gain backend, so I created a package
for that. I started to make some related changes in the beets package
too, but I'm not sure if it's worth the trouble.
If a user (1) installs bs1770gain into their profile, and (2) edits
their config file to use that backend, then the replaygain plugin works
fine. The nix package does a lot of patching to make both of those step
unnecessary, but it seems like overkill to me.
The 'convert' plugin is similar in that it doesn't work OOTB, but it can
be fixed by the user without modifying beets (just install ffmeg or
configure it to use other commands for conversion).
WDYT?
> By the way, Beets says that the next version will be compatible with
> Python 3:
> https://twitter.com/b33ts/status/746871072436289537
>
> When that release comes, let's take the opportunity to update Beets's
> entire dependency graph.
Nice! Sounds good to me.
--
Alex Griffin
next prev parent reply other threads:[~2016-08-03 22:38 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 [this message]
2016-08-07 2:39 ` Leo Famulari
2016-08-08 19:55 ` Alex Griffin
2016-08-09 2:48 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1470263920.2786216.685350833.2EB326FC@webmail.messagingengine.com \
--to=a@ajgrf.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.