Plans for a libcdio 2.4.1 release

[rocky]

Google Summer of Code 2026 is over. You can find out about Shiva Kiran Koninty's Summer of Code project here.

Two Rust crates that were created are

• libcdio-cli
• libcdio-rs

There are several small administrative things (with possibly not small impact) I've been planning to do.

So, this discussion.

Rename the libcdio C repository to libcdio-C and rename the master branch to main

This is to acknowledge that there are more libcdio things out there thin the original C project. Most recently, there is the Rust code and repository for the C bindings to Rust. I should probably move the Python binding into the GitHub organization; also, there may be other repositories not in C.

The default branch of git now seems to have switched from master to main. Sigh.

Thoughts?

Reformat all of the libcdio-C code using clang-format

I've been trying this out over the summer, and as best as I can tell, it is not too obtrusive.

Thoughts?

Go over Doxygen docs.

Shiva mentioned that we can tag stuff using Markdown in Doxygen, and doing that is a lot less ugly than the native Doxygen format.

I haven't gone over the docs in a while.

Final 2.4.1 release

@acts-1631 has been doing great work reviewing the image library and other libraries to ensure bounds aren't exceeded and that malformed image files or filesystem images can't cause damage.

That, along with the above, will go into the 2.4.1 release.

Again, thoughts or comments?

[acts-1631]

Is the plan to eventually replace this codebase with a rust one? It doesn't sound like that but I want to make sure I understand.

Having 2 unrelated libraries with the same name and function is a bit confusing.

[rocky]

Right now, the libcdio command-line tools in libcdio/src (or libcdio-C/src) have been rewritten using the Rust bindings. That code currently lives in libcdio-cli. Although these command-line tools are not a complete replacement yet, for what they do, they are generally more user-friendly and more easily extended by this generation of programmers.

The C tools cd-info, cd-drive etc. will remain in libcdio-C for a while. The Rust names are slightly different:

• drive-info (for cd-drive)
• iso-cp (for iso-read)
• iso-ls (for iso-info)
• mmc-cli (for mmc-tool)

So no, the libraries are not the same, and the installed command-line tools do not have the same name either.

[acts-1631]

Okay, I understand the situation a bit better. Thanks.