Replies: 1 comment
|
Instead of a 3.0.0 release, I am now thinking that the release that removes the CLI utilities would be called 4.0.0. That will leave 3.x for one more major revision of libcdio as it currently stands. There may never be a 3.0.0 release, but we may as well reserve that slot. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Note: Things have changed since the first draft of this discussion
@skr4n has been doing great work this summer on building an MMC library in Rust.
Along with that, he's also identified several bugs in libcdio.
We plan to have three distinct packages under the libcdio umbrella:
iso-read,iso-info, etc). Currently, it implements four of the eight command-line programs in C libcdio. We plan to remove the utility programs from libcdio in a 3.0.0 release when all the programs get ported. For a while, there will be parallel development of libcdio 2.4.x along with libcdio 3.xlibcdio-rsandlibcdio-cliwill have their first public release just before the end of Google's Summer of Code (around the end of August).In the first release,
libcdio-rscontains only Rust-based code to handle MMC commands. These are used only inlibcdio-cli.I welcome your thoughts and comments.
All reactions