Re:Azul3D – A 3D game engine written in Go
by AYBABTME on Thursday August 07, 2014 @10:30PM
(#8151154)
That's one way of doing it. Another is to just use their github path and use vendoring tools like godep.
I prefer vendoring since it doesn't rely on a 3rd party being online or existing in a year. Also it's simpler when you want to have repeatable builds, since the vendored code is usually in your repo. It's also convenient for CI/CD things, since your repo ships as a unique component.
Also using versioned path like that means that a version bump means editing all your files. Across a large project, it becomes harder to manage.
However, versioned path aren't incompatible with vendoring tools. So one doesn't prevent the other.
FWIW, I think versioned path is also not very popular in the pseudo-contest of vendoring code/versioning path.
I prefer vendoring since it doesn't rely on a 3rd party being online or existing in a year. Also it's simpler when you want to have repeatable builds, since the vendored code is usually in your repo. It's also convenient for CI/CD things, since your repo ships as a unique component.
Also using versioned path like that means that a version bump means editing all your files. Across a large project, it becomes harder to manage.
However, versioned path aren't incompatible with vendoring tools. So one doesn't prevent the other.
FWIW, I think versioned path is also not very popular in the pseudo-contest of vendoring code/versioning path.