On Thu, 5 Jan 2017 02:09:24 -0800 (PST) Aurélien Desbrières <aurelien.desbrie...@gmail.com> wrote:
> Vendor?? you mean I have to pay to write software? I have to pay to > use a lib? I suppose you were actually trying to reply to this remark by Ian Davis: > Vendor the library using Go's vendoring support. Then you will always > have a copy of the code you need. Well, this is just a terminology issue. "Vendoring" is a term colloquially used to mean integrating 3rd-party code required by your own project into your project -- in a special way. Since version 1.5 Go has minimal native support for vendoring by giving a special treatment to a directory named "vendor" located right under the top-level directory of a Go project: when building, the Go compiler first tries to locate the package your code imports in that directory. This means, you can take any external library, place its source code under the directory named "vendor" in your project and just keep it there (and check it into the version control system you're using). Note that vendoring has both strong and weak qualities--just like any other approach to depending on a 3rd-party software. Heaps and heaps of words were written on this topic so I won't repeat them. Just google for golang+vendoring and see what's written about this. Several related notes: * When writing production code, you have to check the licenses of the libraries you intend to vendor: they must be compatible with the way your code is licensed (or used/deployed -- if it's for private use). * There's nothing wrong for paying for a 3rd-party library even though we're supposedly discussing F/OSS now ;-) [...] -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
