What do you guys think of adding a contrib directory? #3
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I have a separate utility, sacdinfo, written against libsacd. It's a simple thing to extract the metadata from the SACD files and print it, or write it to a file, in plain text or JSON. How do you feel about making a contrib directory and adding this, and perhaps eventually some other utilities which could be written against libsacd there, for distribution with the main utility?
Included in this request are the sacdinfo utility and related documentation, some changes to the main Makefile with new rules to build the contrib directory, and a minor update to the main README.md which fixes the formatting on the usage.