News for hackers. Stuff that matters.

A comment on A Roadmap to Merging 'dep' into the Go Toolchain. Parent comment

Re:A Roadmap to Merging 'dep' into the Go Toolchain by eikenberry on Thursday March 09, 2017 @05:16PM (#13834333)
But they all have to vendor as well if they want reliable builds. Otherwise you end up with everything breaking when a developer decides to do a forced push or take his repo off github.
[ Parent | on HN ]
Re:A Roadmap to Merging 'dep' into the Go Toolchain by zellyn on Thursday March 09, 2017 @06:18PM (#13834785)
Well, you can vendor, or you can have an internal mirror/cache of repositories.
[ Parent | on HN ]
Re:A Roadmap to Merging 'dep' into the Go Toolchain by sdboyer on Thursday March 09, 2017 @07:21PM (#13835181)
Force pushes - by far more common than straight-up repository removal - are handled without problem; we let you stick with your old version. (At least, that's how it should be - there might be a couple more test cases to write. I know I designed for this problem early on).

Repo removal, renaming, or whatever, are still problems, for sure.

Today, dep populates vendor/ with dependencies, and works equally well whether you decide to commit them or not.

[ Parent | on HN ]
Re:A Roadmap to Merging 'dep' into the Go Toolchain by stepik777 on Thursday March 09, 2017 @05:23PM (#13834393)
Not if there is a central repository which doesn't allow removal of packages.
[ Parent | on HN ]