I understand that timemachine expects only two arguments before the ---separated rsync options.
timemachine passes those "rsync options" after the -- as a whole to rsync. This means that if those arguments contain one or more paths that rsync will accept, it will completely change the meaning of the generated rsync command-line, leading to unexpected behavior.
I don't think there's a way around this, apart from actually parsing the rsync options... 😱
(If only because they can be in either --option=value or --option value forms, forcing the tool to know them in accurate detail.)
I understand that
timemachineexpects only two arguments before the---separatedrsyncoptions.timemachinepasses those "rsync options" after the--as a whole torsync. This means that if those arguments contain one or more paths thatrsyncwill accept, it will completely change the meaning of the generatedrsynccommand-line, leading to unexpected behavior.I don't think there's a way around this, apart from actually parsing the
rsyncoptions... 😱(If only because they can be in either
--option=valueor--option valueforms, forcing the tool to know them in accurate detail.)