On Wed, Aug 03, 2016 at 05:38:40PM -0500, Alex Griffin wrote: > 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?
I don't know how we've handled plugins, in general, so far. I think there is an interesting approach to ALSA plugins on this branch: https://notabug.org/Jookia/guix/commits/WIP_av In the meantime, asking users to configure them manually seems fine. But maybe I'm biased — I literally only use Beets to copy new music into my library based on the music metadata tags. No plugins for me :) Do you know how it works for Beets on "traditional" distros?
