Vendoring MUST stay. Athens is another piece of software that has to be set
up and keep update. Venoring solves this porblem and ols the one when
dependencies go missing.
On Saturday, November 17, 2018 at 5:33:55 AM UTC+1, Henry wrote:
>
> Hi,
>
> It seems to me that go modules and vendor
The main issue tracking vendoring-related discussion is
https://github.com/golang/go/issues/27227
On Thu, 22 Nov 2018 at 09:08, wrote:
>
> Vendor must be kept for when dependencies are no longer available online.
>
> On Saturday, 17 November 2018 04:33:55 UTC, Henry wrote:
>>
>> Hi,
>>
>> It
Vendor must be kept for when dependencies are no longer available online.
On Saturday, 17 November 2018 04:33:55 UTC, Henry wrote:
>
> Hi,
>
> It seems to me that go modules and vendor attempt to solve the same
> problem. I wonder whether we should just choose one and scrap the other, or
>
> People keep adding stuffs into Go and later find themselves unable to
remove existing features due to the backward compatibility promise. Go 1.11
is a different beast than Go 1.0, and is significantly more complex.
For what it's worth, I don't believe that tooling is covered under
the backward
I recall reading from Russ Cox that vendoring will be removed in the future
and be replaced by explicit caching with modules.
--
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,
