Skip to content
This repository was archived by the owner on Sep 9, 2020. It is now read-only.

Commit 901397a

Browse files
committed
Quoting sdboyer & adding links
1 parent e1dec06 commit 901397a

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

docs/FAQ.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -281,9 +281,10 @@ This is the only symbolic link support that `dep` really intends to provide. In
281281

282282
## Does `dep` support relative imports?
283283

284-
Dep doesn't allow relative imports. It's one of the few cases in which dep restricts what the Go toolchain allows (although the toolchain already frowns heavily on them, so tread carefully!)
285-
286-
Dep doesn't support them because of the difficulty required trying to prove that a '../' import doesn't escape the tree of the project.
284+
No.
285+
> dep simply doesn't allow relative imports. this is one of the few places where we restrict a case that the toolchain itself allows. we disallow them only because:
286+
> i. the toolchain already frowns heavily on them
287+
> ii. it's worse for our case, as we start venturing into [dot dot hell](http://doc.cat-v.org/plan_9/4th_edition/papers/lexnames) territory when trying to prove that the import does not escape the tree of the project -[@sdboyer in #899](https://github.com/golang/dep/issues/899#issuecomment-317904001)
287288
288289
## Best Practices
289290
### Should I commit my vendor directory?

0 commit comments

Comments
 (0)