-
Notifications
You must be signed in to change notification settings - Fork 1k
case-insensitive import collision - Sirupsen vs sirupsen #1010
Comments
yeah, this is definitely a problem. and, actually, something i do think we can do something about. though our power to actually achieve a good solution is limited. several issues on this already - #797 #806 #433 (so gonna close this as dupe). you've also discovered the interesting tidbit, first shared in #433 (comment), that even on case-sensitive filesystems, the compiler will reject these. that sorta makes it easier for us, as it makes it OK for us to create global satisfiability rules the solver can enforce to detect and reject these situations. that's nice, because people won't get build or checkout errors, but still crappy, because it means some projects are just literally incompatible with having their dependencies flattened together simply because of variances in import case. we can get through this, it's just going to take some elbow grease. |
Thanks @sdboyer and sorry for the dupe! I had searched elsewhere for this issue, but not the place I was posting the issue! Sorry for the noise. |
What version of Go (
go version
) anddep
(git describe --tags
) are you using?What
dep
command did you run?What did you expect to see?
I expected the program to run.
What did you see instead?
Context
github.com/Sirupsen/logrus
renamed togithub.lhy31512.workers.dev/sirupsen/logrus
(they lowercased the firstS
inSirupsen
).github.lhy31512.workers.dev/bradleyfalzon/dep-case-collision
imports the oldgithub.lhy31512.workers.dev/Sirupsen/logrus
github.com/sirupsen/logrus
, in this case it's our main package.Is there anything
dep
can do about this?I would like to note,
go get
can't handle this either:But fortunately there's a workaround by moving one of the copies to $GOPATH (or removing one from vendor and go getting it):
I don't know what the solution is here, in part I'm posting it because the workaround is good enough for me and might help others, but I'd like to know what's dep's thoughts on this, and probably the go team too.
The text was updated successfully, but these errors were encountered: