Repository navigation
Keep tools inside the workspace through symlinks - #15
Open
stephankaag wants to merge 1 commit into
Open
stephankaag wants to merge 1 commit into
stephankaag wants to merge 1 commit into
Conversation
Workspace#resolve compared a path's spelling with the root, so a symlink inside the workspace that led outside let read and list reach whatever it pointed at, and write create files there. A cloned repository can bring such a link, and code run in the workspace can make one. A path is now judged by where it really leads: the part that exists with its links resolved, then the rest, which a write would create, against the root as the file system knows it. A broken link on the way is refused, since a write would follow it anywhere. Links that stay inside keep working.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Workspace#resolvecompares a path's spelling with the root. A symlink inside the workspace that leads outside it letsreadandlistreach whatever it points at, andwritecreate files there. A cloned repository can bring such a link, and code run in the workspace can make one withln -s ~/.ssh keys.Now a path is judged by where it really leads: the part that exists, with its links resolved, then the rest, which a write would create, against the root as the file system knows it (on macOS
/varis/private/var). A broken link on the way is refused, since a write would follow it anywhere. Links that stay inside keep working.Specs cover a file and a new file through a link that leads out, the link itself, a broken link, links that stay inside, globs leaving outside links out, new files in folders that do not exist yet, and a root reached through a link.