mojo/dart/apptest/pubspec.lock - Issue 1063233004: Teach dart_package to understand the packages/ subdirectory

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: mojo/dart/apptest/pubspec.lock

Issue 1063233004: Teach dart_package to understand the packages/ subdirectory (Closed) Base URL: https://github.com/domokit/mojo.git@master

Patch Set: Remove dart-packages Created 5 years, 8 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

OLD	NEW
(Empty)
	1 # Generated by pub
	tonyg 2015/04/08 13:52:37 It seems worth documenting the process of updating It seems worth documenting the process of updating the locked versions in a README.md somewhere. Is it something like, rm this file, manually pub get, then check in the new one? Or is there a better way? blundell 2015/04/09 11:53:41 You update pubspec.yaml and then run "pub upgrade" Show quoted text On 2015/04/08 13:52:37, tonyg wrote: > It seems worth documenting the process of updating the locked versions in a > README.md somewhere. Is it something like, rm this file, manually pub get, then > check in the new one? Or is there a better way? You update pubspec.yaml and then run "pub upgrade". Do you see a good place to document this? tonyg 2015/04/09 12:55:56 One idea for a follow-up patch would be to output Show quoted text On 2015/04/09 11:53:41, blundell wrote: > On 2015/04/08 13:52:37, tonyg wrote: > > It seems worth documenting the process of updating the locked versions in a > > README.md somewhere. Is it something like, rm this file, manually pub get, > then > > check in the new one? Or is there a better way? > > You update pubspec.yaml and then run "pub upgrade". Do you see a good place to > document this? One idea for a follow-up patch would be to output warnings with instructions when newer packages are available. Then everyone running gclient sync would know it is time to attempt a roll.
	2 # See http://pub.dartlang.org/doc/glossary.html#lockfile

	3 packages:

	4 matcher:

	5 description: matcher

	6 source: hosted

	7 version: "0.11.4+4"

	8 path:

	9 description: path

	10 source: hosted

	11 version: "1.3.4"

	12 stack_trace:

	13 description: stack_trace

	14 source: hosted

	15 version: "1.2.4"

	16 unittest:

	17 description: unittest

	18 source: hosted

	19 version: "0.11.5+4"

OLD	NEW

« build/module_args/mojo.gni ('K') | « mojo/dart/apptest/BUILD.gn ('k') | mojo/dart/apptest/pubspec.yaml » ('j') | mojo/dart/apptest/pubspec.yaml » ('J')