Skip to content

Ignore Cargo.lock#50

Merged
cburgdorf merged 1 commit intonickel-org:masterfrom
janpantel:cargo_lock
Aug 3, 2014
Merged

Ignore Cargo.lock#50
cburgdorf merged 1 commit intonickel-org:masterfrom
janpantel:cargo_lock

Conversation

@janpantel
Copy link
Copy Markdown
Contributor

Cargo has introduced the Cargo.lock file. This should be ignored :)

cburgdorf added a commit that referenced this pull request Aug 3, 2014
@cburgdorf cburgdorf merged commit cef688f into nickel-org:master Aug 3, 2014
@cburgdorf
Copy link
Copy Markdown
Member

Thanks

@ghost
Copy link
Copy Markdown

ghost commented Aug 4, 2014

@janpantel Why should Cargo.lock be ignored? I currently can't find any documentation on it, but if it's like Gemfile.lock for Ruby's Bundler, it should be added to the repository because it allows a consistent set of dependency versions to be used (until explicitly updated with cargo update).

@cburgdorf
Copy link
Copy Markdown
Member

I just read up on what the Gemfile.lock is and I tend to agree that we should put it into version control. However @steveklabnik and @wycats, according to this thread think it should only be checked in for bin projects, not libs.

@janpantel
Copy link
Copy Markdown
Contributor Author

Looking at this from the PHP perspective it's the same approach... Ignore the Composer.lock for lib and check in for 'bin'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants