-
Notifications
You must be signed in to change notification settings - Fork 286
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
Use a mktemp random directory for installation (repeated PR) #301
Conversation
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.
rmTempDir
is a nice addition for cleanup, but a call to that at the end seems to be missing. Thus temp files are only cleaned up in case of a failure currently. Or is fail_trap
naming wrong?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It is not stale, it is just not getting attention. Needs merging :) |
yep, the trap is on Maybe |
Sorry I was confused there for a second, thanks for clearing that up. Its now not only waiting for a failure anymore, so naming is bit wrong. I think |
Do not hardcode a static directory for temporary files, as it might cause problems when running in a multi-user system (ie: orphan files owned by other users). Use mktemp -d instead. Fixes databus23#241
f4351b3
to
a457651
Compare
@ohartl OK, I rebased and renamed the function |
@databus23 Needs merging |
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.
LGTM. Thanks a lot for your contribution
Do not hardcode a static directory for temporary files, as it
might cause problems when running in a multi-user system
(ie: orphan files owned by other users).
Use mktemp -d instead.
Fixes #241
This was already tested in #269