-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: allow globs in source paths #10
Comments
I've referenced a one-line change that lets the shell expand globs. |
Currently if a source path/directory does not exist, tarsnapper emits an error. Eg this:
gives:
The tip of my branch eliminates this code (which would not work with shell expansions) and relies on tarsnap error reporting, which gives more specific errors anyway:
|
The reason the warning exists is because I had this particular use-case where some backup sources may legitimately not be available at backup time. I don't think I care anymore, and probably no one else does either, so I do believe we could get rid of it. |
Wondering if this was still considered? I would love globbing as well, I'd like to backup the rrd data from a Munin master, but I can't do |
I'd merge a pull request! |
It would be nice if one could include globs in source paths:
to get the equivalent of the shell expression:
While just using Python's glob.glob() would do the trick, perhaps just letting shell expansions operate would be more powerful and reduce surprises (often one tests raw tarsnap commands first before encoding them in tarsnapper).
The text was updated successfully, but these errors were encountered: