Restic --iexclude-file format vs Rustic --iglob-file

[LadyMikea]

Out of curiosity, is there a reason for different exclude format? Restic --iexclude-file accepts relative path while Rustic iglob-file absolute, so I can't just use Restic filters without modification (not to mention of "!" sign at beginning). Or I missing something?

[aawsome]

Thanks @LadyMikea for your question / request to change the include/exclude settings.

About the reason: The current reason is that rustic uses the ignore crate for getting file lists and uses all its include/exclude features. Hence the format is tailored after what ignore needs as input format and about what ignore features..

But there have been quite some requests regarding includes/excludes (which cannot be adressed by ignore), so I think we'll work on a redesign about this topic. Self-implementing this logic has the additional advantage that on the long run we could support other sources than local fs and just re-use the include/exclude logic.

[aawsome]

But actually I have to add an restriction: rustic does not have the goal to be or stay CLI-compatible with restic. Its goal is to stay repository-compatible - and of course to be feature-complete or even out-feature restic - , but we won't guarantee that your restic commands will work 1:1 when using them with rustic.

[LadyMikea]

Thanks very much for explanation. Of course I understand, Rustic is not a Restic. Manually converting Restic "--iexclude-file=" to Rustic "iglob=" is rather straightforward. If I may ask another question. Bigger problem is lack of Rustic equivalent Restic "--files-from=" option (text file contains list of directories and/or files as a backup source). As I understand Rustic "source = " accepts only paths.