TW

Well, it is helpful if the backup archive has helpful pathes. If you'ld just pick a lot of stuff from misc locations and put it into an archive (without some...

That sounds like a reasonable suggestion, so I am reopening this so we can check whether this can be implemented.

It looks like we can't implement tar syntax and behaviour here (like `-C /home/userA projectA -C /home/userB projectB`). Reasons: - blocker: argparse `parse_args` does not support intermixed options and positional...

A hack to implement the same idea could be to use some special separator within the PATHs, like: ``` borg create REPO::ARCHIVE /home/userA::projectA /home/userB::projectB ``` Presence of `::` inside a...

@rovo89 Oh, that's an interesting, slightly dirty hack. :-) It's somehow similar to my idea back then: https://github.com/borgbackup/borg/issues/4685#issuecomment-1007716496 But, as it uses the unusual, but "NOP" `./` as the separator,...

@rovo89 yes, i tagged #8060 with port/master. just want to first collect all feedback, see also the 1.4 thread on github discussions.

OK, I'll summarise the ideas here (I always used `/./` as separator here): - SP "strip prefix" `/strip/prefix/./keep/postfix` - implemented by #8060 - SM "strip in the middle" `/keep/prefix/./strip/this/./keep/postfix` -...

Guess this is solved?

I guess we can have some hope that this will be just a cosmetic problem with the warning while `1.1-maint` branch is still supported. So, guess this ticket should be...

1.1.18 was last 1.1.x release, thus no change there. 1.2-maint still uses `setup_requires` in `setup.py`, but already has a `pyproject.toml` with `build-requires`, so we can just remove the entry in...