Skip to content
This repository has been archived by the owner on Feb 26, 2019. It is now read-only.

godep save should not update existing packages by default #65

Closed
kr opened this issue Mar 10, 2014 · 1 comment
Closed

godep save should not update existing packages by default #65

kr opened this issue Mar 10, 2014 · 1 comment
Assignees
Labels

Comments

@kr
Copy link
Member

kr commented Mar 10, 2014

By analogy with 'go get'.

Running godep save with no flags should keep already-saved dependencies as they are, and only add missing packages. Running godep save -u will then be necessary to update versions.

@kr kr added the enhancement label Mar 10, 2014
@kr kr self-assigned this Mar 22, 2014
kr added a commit that referenced this issue Apr 7, 2014
This changes the default behavior of 'godep save' so as
to preserve any dependencies already in the list at the
revision they were previously saved at. New dependencies
will be added, and old dependencies will be removed, but
that's all. This makes the save command roughly
analogous to 'go get' with no flags.

PENDING:
We also introduce a new command, 'godep update', to
update one or more dependency versions. This is roughly
analogous to 'go get -u'. This is a separate command
(rather than 'godep save -u') because the package
argument is different: it specifies a dependency rather
than a top-level package.

fixes #65
kr added a commit that referenced this issue Apr 7, 2014
This changes the default behavior of 'godep save' to
preserve any dependencies already in the list with their
existing revision. New dependencies will be added, and
old dependencies will be removed, but that's all. This
makes the save command roughly analogous to 'go get'
with no flags.

PENDING:
We also introduce a new command, 'godep update', to
update one or more dependency versions. This is roughly
analogous to 'go get -u'. This is a separate command
(rather than 'godep save -u') because the package
argument is different: it specifies a dependency rather
than a top-level package.

fixes #65
kr added a commit that referenced this issue Apr 7, 2014
This changes the default behavior of 'godep save' to
preserve any dependencies already in the list with their
existing revision. New dependencies will be added, and
old dependencies will be removed, but that's all. This
makes the save command roughly analogous to 'go get'
with no flags.

PENDING:
We also introduce a new command, 'godep update', to
update one or more dependency versions. This is roughly
analogous to 'go get -u'. This is a separate command
(rather than 'godep save -u') because the package
argument is different: it specifies a dependency rather
than a top-level package.

fixes #65
kr added a commit that referenced this issue Apr 10, 2014
This changes the default behavior of 'godep save' to
preserve any dependencies already in the list with their
existing revision. New dependencies will be added, and
old dependencies will be removed, but that's all. This
makes the save command roughly analogous to 'go get'
with no flags.

PENDING:
We also introduce a new command, 'godep update', to
update one or more dependency versions. This is roughly
analogous to 'go get -u'. This is a separate command
(rather than 'godep save -u') because the package
argument is different: it specifies a dependency rather
than a top-level package.

fixes #65
@kr kr closed this as completed in ab7936a Apr 16, 2014
@drewwells
Copy link

Should godep save automatically update dependencies? If godep save is the exact opposite of godep restore, I would expect save to update vendored packages from the newer ones in gopath. It appears only godep update ./... does this, or rm -rf Godeps; godep save ./...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants