Skip to content
This repository was archived by the owner on Feb 22, 2018. It is now read-only.

Put pubspec.lock under source control #87

Closed
vicb opened this issue Feb 14, 2014 · 14 comments
Closed

Put pubspec.lock under source control #87

vicb opened this issue Feb 14, 2014 · 14 comments

Comments

@vicb
Copy link
Contributor

vicb commented Feb 14, 2014

As angular is moving really fast, users encounter issues trying the examples.

Versionning the lock file could help them by making sure that the dependencies are at a working version.

@savantmohan
Copy link

@vicb :

What could be possible solution for this. Kindly explain in detail as i am new to angular dart environment.

@zoechi
Copy link

zoechi commented Feb 26, 2014

@savantmohan
Copy link

@zoechi That issue was posted by me only :)

@vicb
Copy link
Contributor Author

vicb commented Feb 26, 2014

@savantmohan there's probably a problem with version mismatch that comes form pubspec.lock not being versionned. This is what is requested by the linked issue. There's really nothing we can do in this repo for that.

Edit: I thought I was posting in angular.dart..., here is the right place

@zoechi
Copy link

zoechi commented Feb 26, 2014

@savantmohan I know. I just wanted to connect them.

@kwalrath
Copy link
Contributor

Would it work to just change pubspec.yaml to have a specific version, rather than "any"?

@vicb
Copy link
Contributor Author

vicb commented Feb 26, 2014

the .lock file has more versions (includes dependencies) so having the lock file versionned is really the best bet.

@kwalrath
Copy link
Contributor

@mhevery, @traceypowersg, @shailen: What's your opinion on putting the AngularDart tutorial's pubspec.lock under version control? At the very least, we should change pubspec.yaml to have a specific version of angular, but @vicb thinks that's not enough.

@vicb
Copy link
Contributor Author

vicb commented Feb 26, 2014

@kwalrath this page has some useful information and the linked session states:

If your package is for an app, you check your lockfile into your source control system! That way, everyone on your team will be using the exact same versions of every dependency when they build your app.

edit:
and towards the end, there's an explanation of why concrete versions in pubspec.yaml is a bad idea:

But depending on single concrete versions is too precise and with shared dependencies leads to version lock.

@kwalrath
Copy link
Contributor

@vicb, I even wrote something about that (way back when): https://www.dartlang.org/tools/private-files.html#pubspeclock

OK, you're right, we should check in pubspec.lock. And have someone responsible for updating it from time to time.

@kwalrath
Copy link
Contributor

Any volunteers? :)

@vicb
Copy link
Contributor Author

vicb commented Feb 26, 2014

I would love to see angular adopting semver, see dart-archive/angular.dart#612

This way it would be easier to upgrade the lock files on BC breaks... But I guess pre-1.0 every single version might break BC.

@vicb
Copy link
Contributor Author

vicb commented Feb 26, 2014

@kwalrath I think you should open a ticket. You'll probably be able to find a volunteer in the community.

@kwalrath
Copy link
Contributor

Fixed. Thanks, @vicb!

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

No branches or pull requests

4 participants