-
Notifications
You must be signed in to change notification settings - Fork 1k
Feedback: Existing project using gvt vs. dep #138
Comments
Thanks for trying it out and providing feedback! 🎉 🎉
Some of that time is initial repository clones - a one-time cost. But yeah, we've not overly prioritized towards performance just yet. That said, there is a plan, and there's a lot of headroom here: #67
This is weird. Could you open an issue specifically for this, please, and provide a little more context about the state of your GOPATH when you ran
I don't know gvt well, but I'm pretty sure that yeah, this is accounted for by the is the difference between "package" and "project." The latter is defined in the spec doc, but that's a bit loose, so the definition in gps might also be helpful.
Possible? Again, idk gvt that well - @jessfraz might be able to say more definitively. The question of what ultimately ends up in vendor is a bit of a thing itself, too - see #120. |
fwict i think gvt is just pulling in whole repos and their deps but idk,
there was a later version in gvt that i started using and was confused
because it was pulling in more than an ealier one, and it kinda made me
sad, but i'm in a pro-prune all the things camp
…On Tue, Jan 24, 2017 at 2:53 PM sam boyer ***@***.***> wrote:
Thanks for trying it out and providing feedback! 🎉 🎉
dep init is slow. It took more than 2 minutes to complete on a high-end
machine with a 100Mbps connection. I didn't check what the bottleneck is
and I understand if performance is not a high priority at this stage.
Some of that time is initial repository clones - a one-time cost. But
yeah, we've not overly prioritized towards performance just yet. That said,
there is a plan, and there's a lot of headroom here: #67
<#67>
After dep init, manifest.json has an empty JSON object: {}
This is weird. Could you open an issue specifically for this, please, and
provide a little more context about the state of your GOPATH when you ran dep
init? Thanks!
lock.json has entries, but it only found 26 "projects", compared to 44
dependencies with gvt. See below.
I don't know gvt well, but I'm pretty sure that yeah, this is accounted
for by the is the difference between "package" and "project." The latter is
defined in the spec doc
<https://docs.google.com/document/d/1qnmjwfMmvSCDaY4jxPmLAccaaUI5FfySNE90gB0pTKQ/edit>,
but that's a bit loose, so the definition in gps
<https://godoc.org/github.com/sdboyer/gps#ProjectRoot> might also be
helpful.
I've tried creating vendor/ with both dep ensure and gvt restore and the
resulting project compiles fine in both cases, so I'm inclined to think
gvt includes some unnecessary deps.
Possible? Again, idk gvt that well - @jessfraz
<https://github.com/jessfraz> might be able to say more definitively. The
question of what ultimately ends up in vendor is a bit of a thing itself,
too - see #120 <#120>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#138 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABYNbAEtUSbA0xkkxGxUWR2guC3cAFIBks5rVoEBgaJpZM4Ls1xF>
.
|
Opened #149.
Yes, |
Yes, gvt pulls in whole repos (expect the tests) as @jessfraz stated. I ran into that exact issue in the past and had to manually vendor a subset of the files. Dep is much nicer in that regard 👍 @dcelasun Can this ticket be closed or are there still outstanding issues? I opened up a new issues, #679, to address smoothing out the transition from gvt. As far as speed, I just ran Hopefully the strange JSON {} issue disappeared in the transition to .toml files. Cheers! |
Yep, it looks quite a bit faster to me too.
The problem wasn't about the format, but it still got "fixed" (depending on how you look at it) in another way. As you also realized in #679, Since I don't have any dependencies under But yes, I guess we can close this one since #679 has most of my concerns. |
It's a little more sophisticated than that - https://github.com/golang/dep/blob/master/FAQ.md#how-does-dep-decide-what-version-of-a-dependency-to-use It may just be that all the dependencies your project has have no tagged semver releases, so master is the best it can do.
Indeed, the solution here is writing a gvt adapter that knows how to translate from gvt's metadata into dep's. We should be able to start work on that shortly after #500 is merged. That should be this week. 🎉 |
Just tried this on an existing project. I've only been playing with this for a few minutes, so it's quite possible I'm doing something wrong. That said, I'm really excited to see official progress on dependency management! Thank you for working on this!
Quick thoughts:
dep init
is slow. It took more than 2 minutes to complete on a high-end machine with a 100Mbps connection. I didn't check what the bottleneck is and I understand if performance is not a high priority at this stage.dep init
,manifest.json
has an empty JSON object:{}
lock.json
has entries, but it only found 26 "projects", compared to 44 dependencies withgvt
. See below.vendor/
with bothdep ensure
andgvt restore
and the resulting project compiles fine in both cases, so I'm inclined to thinkgvt
includes some unnecessary deps.lock.json
manifest (from gvt)
The text was updated successfully, but these errors were encountered: