Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow passing in a custom path to the tarsnapper binary #52

Open
jeffwidman opened this issue Dec 31, 2018 · 1 comment
Open

Allow passing in a custom path to the tarsnapper binary #52

jeffwidman opened this issue Dec 31, 2018 · 1 comment
Labels
feature

Comments

@jeffwidman
Copy link
Contributor

tarsnapper expects tarsnap to be in the PATH, but that's not always true, for example under cron (#18).

So it'd be nice to be able to specify a custom path to the tarsnap binary, rather than having to always remember to modify PATH
@miracle2k
Copy link
Owner

We already have -o for tarsnap options, I could see a --tarsnap-bin or --exec argument or something similar.

@jeffwidman jeffwidman mentioned this issue Jan 16, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@miracle2k @jeffwidman