Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

all: dep still looks like the official package manager for Go #35894

Open
flibustenet opened this issue Nov 28, 2019 · 6 comments
Open

all: dep still looks like the official package manager for Go #35894

flibustenet opened this issue Nov 28, 2019 · 6 comments

Comments

@flibustenet
Copy link

@flibustenet flibustenet commented Nov 28, 2019

There is still people think dep is the official package manager (around social networks). The github pages looks like it is and they are under the umbrella of go team.
https://golang.github.io/dep/

Dependency management for Go
Copyright © 2018 The Go Authors

The "blog" doesn't speak about modules.
https://github.com/golang/dep/
doesn't mention modules, ask for funding...

It's fine if dep can continue to be improved to make smooth transition to modules or live by it's own, but it looks very ambiguous for newcomer or people not reading blog.golang.org

@agnivade

This comment has been minimized.

Copy link
Contributor

@agnivade agnivade commented Nov 29, 2019

FWIW, the README is pretty clear about it:

dep was the "official experiment." The Go toolchain, as of 1.11, has adopted an approach that sharply diverges from dep. As a result, we are continuing development of dep, but gearing work primarily towards the development of an alternative prototype for versioning behavior in the toolchain.

And the dep source files are under the standard Go BSD License

// Copyright 2016 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

So I think the part about Copyright © 2018 The Go Authors is correct too.

From what it looks like, the dep folks plan to keep working on it. So it would be unfair to outright declare - "please don't use dep, use Go modules". But perhaps the wording can be made more clear.

In any case, I think this is something that you can raise with the dep team by opening an issue there.

/cc @kevinburke who seems to manage dep now.

@ALTree

This comment has been minimized.

Copy link
Member

@ALTree ALTree commented Nov 29, 2019

@agnivade

FWIW, the README is pretty clear about it:

dep was the "official experiment." The Go toolchain, as of 1.11, has adopted an approach that sharply diverges from dep. As a result, we are continuing development of dep, but gearing work primarily towards the development of an alternative prototype for versioning behavior in the toolchain.

IMO this is not clear at all.

The Go toolchain [...] has adopted an approach that sharply diverges from dep

What approach? It's not mentioned, and there are no links to the module system announcement. There should be.

[gearing work primarily towards] the development of an alternative prototype

This statement is very outdated. What here is called "an alternative prototype" (the module system) is no longer a prototype, and it has been fully adopted by the project. A newcomer reading this will get a completely wrong idea about the status quo of package management in Go.

@agnivade

This comment has been minimized.

Copy link
Contributor

@agnivade agnivade commented Nov 29, 2019

You are right, those parts need to be updated.

@mvdan

This comment has been minimized.

Copy link
Member

@mvdan mvdan commented Nov 29, 2019

I agree that there's still too much confusion out there. Particularly for folks who only use Go sporadically - I've encountered multiple of those who simply tried to continue using dep, as the official site and docs didn't mention anything else that should be considered.

I personally think that, if dep is to continue under the Go organization, it should clearly point to modules. Not necessarily as "use modules instead", but at least as "the standard for publishing and using Go packages today is modules".

@richterk

This comment has been minimized.

Copy link

@richterk richterk commented Nov 30, 2019

Honestly, the documentation for modules is VERY verbose and not altogether very helpful. For instance, I've been trying to convert my projects over to modules for several hours now, and can't (even with the help of the documentation) figure out what combination of folders/go.mod files I need to make it work. Dep at the very least was easy to use/figure out.

@dmitshur

This comment has been minimized.

Copy link
Member

@dmitshur dmitshur commented Dec 2, 2019

@andybons andybons changed the title dep still look like the official package manager all: dep still looks like the official package manager for Go Dec 2, 2019
@andybons andybons added this to the Unreleased milestone Dec 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.