media-sound/beets (updated) in your overlay? #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Conflicts: media-sound/beets/beets-1.3.6.ebuild
There are plugins that require "indirect dependencies", i.e. required tools are given by configuration paths. See http://beets.readthedocs.org/en/v1.3.6/plugins/replaygain.html#mp3gain-and-aacgain as example. Dependencies like these has been removed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello Laurent.
I'm using media-sound/beets, a very powerful command -line tool to manage music metadata: http://beets.radbox.org/
New versions depend on dev-python/enum34 (in your overlay).
I've seen also that you are interested in audio fingerprint (managed by beets) and in picard (the GUI sibling of beets).
So, you can be interested in recent versions of beets.
Please, consider that I'm a beginner as ebuild writer.
Regards,
HUjuice