enhancement: file pattern support for tar command

[Kalmalyzer]

I would like to use desync tar to upload parts of the result from a build process. I can do so today, by copying parts of the build process output to a temp directory, and then performing desync tar on the whole tree. It would however be preferable to skip that copying step.

Looking a bit at the current implementation, it seems that the tar & untar commands create some sort of local filesystem representation at the specified location. One syntax that could make sense is something along the lines of desync tar <output file> <source base folder> [globbing patterns] where, if no globbing patterns are included, all files will be captured.

Example: desync tar result.catar input input/binaries/* input/readme.txt would capture the binaries subtree and the readme.txt file from the input folder and put it into result.catar.

Does the above feature design make sense? Would you take a PR for this?

[folbricht]

Think this may work if you change the syntax a bit. desync won't let you put disjoint trees into a catar, but I imagine adding an --include <pattern> and/or --exclude <pattern> could perhaps act as a filter while keeping a single root of the tree. The patterns would have to be relative to the root of the tree as well. Does that sound reasonable and match what you're trying to do? I won't have time to implement it the next couple of weeks at least, but will take PRs if you have something.

[Kalmalyzer]

--include <pattern> and/or --exclude <pattern> would make sense, yes. I'll let you know in case I get around to implement this.