Closed ukari closed 4 years ago
Thanks for reminding me! We've got a big audio PR that stalled, and a minor webcam fix that I built atop the WIP audio work. I'll see if we can land both in the next couple days. If not, then I'll pull the webcam fix back to the trunk version and cut a release from that.
Hi, I would like this as well, do you know when the version will be published? I do not need any of the new functionality, just the base update.
Alright, I'm giving up on the audio branch for now as it seems the author doesn't have time to finish it off. I've uploaded a candidate for version 0.13.
CI is green, but I'd like to hear of someone other than me able to build, and preferably run, this before I publish.
ETA: But just to be clear, if nobody says anything I'll go ahead and publish anyway as this has dragged out for too long.
Can you explain how to test a candidate release? I always upload a candidate before publishing a new release, but then at the "test the candidate" step I realize that I can't specify a candidate version to either cabal or stack, so I end up publishing and then testing the real release.
Huh, I had hoped that this was something that everyone other than me knew as I don't know how to use them either 😂.
I think you can use a cabal.project
file with a URL for the release candidate tar file. If you're already set up to use a local checkout or git repo directly, then there is this branch.
I compiled that branch using ghc 8.10.1 and was able to run the demo successfully.
Thank you @gelisam!
I've pushed 0.13.0 to hackage! Thank you all for the patient reminders to do so.
The documentation did not get built automatically, so I built and uploaded it.
Thank you!
In the hackage the ffmpeg-light package with version 0.12.2.2 has a dependency which need base (>=4.6 && <4.13), while now the newest base package has a verison 4.14.0.0.
links: