To avoid conflicts when importing in other projects (dependency hell
between docker/docker vs docker/engine).
On an external project, I'd get errors like this without this PR:
$ go get github.com/docker/libcompose@master
go: finding github.com/docker/libcompose master
go: finding github.com/docker/docker v0.0.0-00010101000000-000000000000
go: github.com/docker/docker@v0.0.0-00010101000000-000000000000: unknown revision 000000000000
cc @vdemeester
My 2c: In an ideal world everything would use one repo reference (either docker/engine OR docker/docker), and personally I'd almost suggest docker/engine is cleaner due to no moby/moby rename, but I'm not a decision maker on Docker development and keeping a single canonical import is the safe answer right now across the Go ecosystem.
To avoid conflicts when importing in other projects (dependency hell between
docker/docker
vsdocker/engine
).On an external project, I'd get errors like this without this PR:
cc @vdemeester
My 2c: In an ideal world everything would use one repo reference (either
docker/engine
ORdocker/docker
), and personally I'd almost suggestdocker/engine
is cleaner due to nomoby/moby
rename, but I'm not a decision maker on Docker development and keeping a single canonical import is the safe answer right now across the Go ecosystem.