-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Continued development #8
Comments
I wouldn't mind at all if the link changed. I'd also be happy to work some small changes and facilitate more development via PRs being addressed in a meaningful amount of time... |
I have taken the liberty of forking this repo and updated, re-factored and extended the wrapper. https://github.com/SpotlightKid/nim-sndfile @julienaubert Are you interested in incorporating these changes in this repo and maybe releasing a 0.2.0 version? Then please let me know and I'll prepare a PR. I could also help with the release process. If I don't hear anything within, say, a month, I'll probably rename my fork and publish it under the new name to the nimble directory. |
Hi there! Sorry for having left this in limbo. The ping got my email attention. Sounds great for everyone if you would make your fork the official one. |
Thanks for the fast answer! So, if I make a PR at https://github.com/nim-lang/packages/ to update the package URL and post a link to the PR here, can I ask you to post your approval there, so it can get merged? |
@SpotlightKid yes of course |
First of all, thanks for this small wrapper. I noticed that the PR for writing files #7 has not been merged, or any other activity for that matter, in over a year. Currently, I'm using the PR without issues, but it would be great if I could just install it via nimble. Will there be any further updates?
@jamesb93: If there is no more development here, would you be okay if someone changed the URL in the nimble directory to your fork? Are you still using this? Or should I fork your fork, in case people want support?
The text was updated successfully, but these errors were encountered: