3 ms·
> I mean, I guess this is technically true. But seems like it shouldn't be an issue in practice as the API you're calling shouldn't have changed, just the imple
by wtetzner 9y ago
> I mean, I guess this is technically true. But seems like it shouldn't be an issue in practice as the API you're calling shouldn't have changed, just the implementation. If it has changed, then downgrade the dependency?
And if the new implementation has a new bug, you might be screwed. It worked last week, but not this week. How do I get back to the working version?
- lsaferite 9y agoUse 'git bisect' or some similar tool to walk back and find the point where the lock file change triggered the bug?
- wtetzner 9y agoIf you have a lock file, there's no problem. I was arguing about what happens when there isn't a lock file. I may have inferred something that wasn't in the original comment, by reading too many of the other comments on this page.
- makapuf 9y agoSort but given that we're relying on git mostly, what are the advantages of lock files over submodules/subtrees ?
- wtetzner 9y agoWell, that would lock all of the projects into git. What if some libraries are in git, and others are in mercurial and darcs? I think it’s better to have a package manager that’s not reliant on a particular source control system.