-
Notifications
You must be signed in to change notification settings - Fork 63
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/allow var tmp #264
Conversation
…typically a writable space.
…just the tests to account for it
…low rpmbuild to set it
src/VolumeMap.c
Outdated
@@ -585,6 +589,7 @@ int _validateVolumeMap( | |||
const char *from, | |||
const char *to, | |||
VolumeMapFlag *flags, | |||
const char **toExactAllowed, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
space ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doh! i'll fix that
Overall looks good, i would like paths to be configurable. Special paths can be given special consideration. |
the spacing is corrected. It looks like travisci fell apart on the previous push owing to a transient failure at travis. hopefully this push will build. |
re: making paths configurable, i believe that is in-general possible. /var is a little touchy owing to its security issues. I don't think there is any harm in /var/tmp, but other paths within var could be more problematic. We can re-address the overall configurability in a branch focused on that. |
for issue #262