You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 9, 2020. It is now read-only.
Copy file name to clipboardExpand all lines: docs/FAQ.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -281,9 +281,10 @@ This is the only symbolic link support that `dep` really intends to provide. In
281
281
282
282
## Does `dep` support relative imports?
283
283
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)
0 commit comments