Re: cross-platform backup tool Planning for milestone 2.4.0

[Eric Zolf]

Hi,

On 23/11/2022 13:04, Patrik Dufresne wrote:
> Hiu Eric,
>
> Thanks alot for all the good work you have done so far on rdiff-backup. It
> was about time to have someone dedicated like you are to the project.
>
> As for version 2.2.0 I have to re-test, but I've faced a compilation issue
> on MacOS with the latest pip version. I had to revert back to the previous
> version of pip. I'm not sure if it's related to pip or rdiff-backup at this
> point. https://github.com/pypa/pip/issues/11597
> It might be related to the tweak we are doing in setup.py.

From the look of it, it has nothing to do with rdiff-backup but more 
with the way Python/clang is compiling libraries and finding the 
librsync library and include files. I get a similar error message under 
Windows if I forget to define `LIBRSYNC_DIR`. I have no clue of MacOS 
but I'd check how it finds libraries/includes and what could have 
changed with pip in this regard.

> As for version 2.4.0, the list of enhancements is great and will be a good
> improvement to move forward.
> One BIG missing feature that is worth thinking about is to continue a
> backup after a failure.

Yeah, a bit too big for this release I thought. In my eyes rather a 3.0 
topic, once the code has been extensively cleaned-up. I'll keep an eye 
on it though.

KR, Eric

> On Wed, Nov 23, 2022 at 1:57 AM Eric Zolf <ewl+rdiffbackup@lavar.de> wrote:
>
> > Hi,
> >
> > milestone 2.2.0 is nearing its completion, and I've started to think
> > about what I'd like to implement for the next version.
> >
> > If you'd like to have a look, and give feedback, check
> > https://github.com/rdiff-backup/rdiff-backup/milestone/3
> >
> > It's not a promise that everything will be implemented in 2.4 but that's
> > the things I plan to work on, and if they are too hard, then they'll be
> > moved to the next milestone.
> >
> > The background is the need to support the old 200 API aka rdiff-backup
> > v2.0.5. This hinders quite a lot my ability to do big changes, meaning
> > big changes will only happen for 3.0+ (which will be an interesting
> > release, but it's probably a few years until we're there).
> >
> > Hence small steps for now, also not bad...
> >
> > KR, Eric