Project still active?

[nimaim]

Hi, is this project still active? I would love to see a library for partclone. Currently, we are forced to fork() / exec() the proper partclone binaries in our application for any recovery operation. A library API allows for much more flexibility. Of course, however, if this is no longer being maintained, we will continue to use what we have.

[xiangzhai]

@nimaim you can fork libpartclone, it is base on Thomas-Tsai@26d444b commit.

[nimaim]

Hi @xiangzhai, thank you for the response. My question was more is all the logic there to use it right now (i.e. is the C/C++ API files all there and implemented)? I see a lot of TODOs still in the README. Any documentation on how to use it? Does it support reporting progress through a callback function? I see that as one of the critical features. Thanks again.

[xiangzhai]

Does it support reporting progress through a callback function?

support https://github.com/isoft-linux/molly/blob/master/src/parttofilewidget.cpp#L387

Any documentation on how to use it?

sorry no, docs <-- TODO: libpartclone API doc.

is the C/C++ API files all there and implemented

yes https://github.com/isoft-linux/partclone/tree/libpartclone/lib

I see a lot of TODOs still in the README

not 100% finished:

[ ] docs <-- TODO: libpartclone API doc.
[ ] HACKING <-- TODO: code review by analyzer and sanitizer
[ ] src <-- TODO: plugin - change exit to return
[ ] clang-analyzer.sh <-- TODO: clang analyzer for Preprocessed file

about clang static analyzer, there is, of course, false positive, for example: https://bugs.llvm.org/show_bug.cgi?id=31458 but it is able to use clang sanitizer or libfuzzer to dynamically analysis libpartclone.

[nimaim]

@xiangzhai Thank you for the example. I will try some test apps with it in the next week or so.