Re: [Dar-libdar_api] updating kdar to work with libdar 4 (dar 2.3.1)

[Denis C. <dar...@fr...>]

Glen Ogilvie wrote:
> Hi,

Hello Glen,

> 
> I would like to help with getting kdar working with the newer dar
> libraries.  I am a beginner C++  programmer, so will need help, but am
> prepared to spend  time learning and will put in some effort if anyone
> still reads this list.

Cool! That's something I had putted in my list of things to do, but you 
will save me some time doing it. Of course, you can rely on me (using 
this mailing-list) for any help.

I realized afterward that breaking backward compatibility of the API is 
not fair for applications that rely on it, while for some reasons I felt 
(and still feel) good I had to do it.

For the future, I cannot prevent that it will not occure again, but I 
will try to better reduce it and if not possible I will create a 
document that gather the changes to apply to each API call, to keep the 
same behavior, from one API version to the next API version. This will 
be done in a document rather than in this mailing-list for further 
reference and to be used by applications that rely on libdar.

> 
> I've been digging around in the source, but not finding it easy to
> figure out all the new stuff needed to be passed when using new
> libdar::archive in createArchiveThread.cpp.
> 

I see two possibilities to address your need:
- try to compile and look for the error messages
- do a "cvs diff" between the two API version (I will do it right now 
and provide you the interesting part).


> Also,
> 
> Denis Corbin wrote:
> 
>>  By the way, I have quite finished implementing the features I wanted to
>>  include in next major release that have impact on the API. There is one
>>  more feature (the "dar_merge") I have to make room for (a new
>>  constructor for the archive class) then I will freeze the API for new
>>  features. So you will be very welcome to integrate the new features
>>  brought by the next libdar if you like in kdar, eventually give your
>>  feedback for I add the necessary calls I could have not thought about
>>  for it works as you wish. Of course I will first have to give you a
>>  summary of what have changed since previous API and how to use it.
>>
>>  On the path to the release, few other feature are to be implemented that
>>  should not have impact on the API and documentation of the API should
>>  have to be updated, as well as I hope a review of the overall
>>  documentation structure.
>>
> 
> Dennis, have you managed to put togeather a summary of the API
> changes?  It would help in updating kdar to use them.

Yep, I will provide it to you ASAP.

> 
> Regards
> Glen Ogilvie
> New Zealand
> 

Thanks Glen,

Best Regards,
Denis.