Closed yields closed 8 years ago
The workflow for godep update is to first godep restore
, then checkout the version of the package you want to update to, then update.
I see, is there a workaround at all?
Seems to me that godep <pkg>
should update a single package and it's dependencies and not error if another package does not exists, is there a reason for this workflow that i'm missing?
Would love to work on a fix if you're interested :)
I agree. I thought there was a test for this, but maybe not.
Sent from my iPhone
On May 12, 2016, at 08:58, Amir Abu Shareb notifications@github.com wrote:
I see, is there a workaround at all?
Seems to me that godep
should update a single package and it's dependencies and not error if another package does not exists, is there a reason for this workflow that i'm missing? Would love to work on a fix if you're interested :)
— You are receiving this because you commented. Reply to this email directly or view it on GitHub
I thought that
godep update <pkg>
will update the given package, but seems like it "checks" all dependencies and errors if a dependency is not found, even thoughgithub.com/pkg/a
has no dependencies.Any reason to check them all, is there a workaround to updating a single package?