Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Option to use relative paths inside of archive instead of fully qualified ones #11

Closed
d-Rickyy-b opened this issue Dec 21, 2020 · 0 comments · Fixed by #13
Closed

Option to use relative paths inside of archive instead of fully qualified ones #11

d-Rickyy-b opened this issue Dec 21, 2020 · 0 comments · Fixed by #13
Labels
enhancement New feature or request

Comments

@d-Rickyy-b
Copy link
Owner

In a config with a source like /path/to/a/directory/ the resulting archive will also contain a fully qualified path to that exact same directory.

There should be a config variable to enable relative paths. That way the archive would only contain e.g. the name of the backup source directory instead of the whole absolute path.

In the above case, the archive would contain only one dir called directory instead of path/to/a/directory on the root level.

Issue with multiple sources

When using multiple sources and some of the 'relative' paths are the same

.
├── another
│   └── path
│       └── to
│           └── another
│               └── directory
└── path
    └── to
        └── a
            └── directory

In the above example we got 2x "directory" as relative source paths. What should happen to those? Put them into the same dir? Use directory and directory1 etc.?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant