Don't write to parent dir when rendering problem statement #359
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I got bit by this just now, so I decided to fix it. Our archaic setup to render pdf:s prior to this PR involves writing some temporary files (
problemset.clsand a.texfile with a random name) to the parent directory of the problem we're installing). This obviously fails badly if the user running problemtools does not have write access above the problem directory.This PR puts the temporary files in a temporary directory instead. To be able to do so, I had to add a new feature to the cls file, with the new command
\problemparentpath{<path>}, which makes the other commands look for problems in that path, rather than in the current directory.