A Proposal for Package Versioning in Go

Re:A Proposal for Package Versioning in Go by zeveb on Monday March 26, 2018 @02:04PM (#16681020)

> The only explanation for this constant re-invention that I can come up with (and that's shared among others I know) is that Google doesn't care/need a dependency tool because of their mono repo.

That's a pretty good argument for using a monorepo, don't you think? A single organisation's code should all be in a single repo, which means that a single version of a dependency is used within the organisation, and that updating to a new version of that dependency is a single, self-contained project.

[ Parent | on HN ]

Re:A Proposal for Package Versioning in Go by ilovecars2 on Monday March 26, 2018 @03:48PM (#16681878)

We use a monorepo at our place of work and it’s great, so far. We also use govendor to manage external dependencies in the monorepo. We are rigorous about keeping packages up to date so have never had to run v1 and v2 of a package at the same time.

[ Parent | on HN ]