pubspec.yaml - Issue 1142363005: Added .packages, packages/ discovery.

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: pubspec.yaml

Issue 1142363005: Added .packages, packages/ discovery. (Closed) Base URL: https://github.com/dart-lang/package_config.git@master

Patch Set: Created 5 years, 7 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
1 name: package_config	1 name: package_config

2 version: 0.0.1	2 version: 0.0.1

3 description: Support for working with Package Resolution config files.	3 description: Support for working with Package Resolution config files.

4 author: Dart Team <misc@dartlang.org>	4 author: Dart Team <misc@dartlang.org>

5 homepage: https://github.com/dart-lang/package_config	5 homepage: https://github.com/dart-lang/package_config

6	6

7 environment:	7 environment:

8 sdk: '>=1.11.0-dev.0.0 <2.0.0'	8 sdk: '>=1.11.0-dev.0.0 <2.0.0'

9	9

	10 dependencies:

	11 charcode: '^1.1.0'

	12 path: "any"

	13 http: "any"
	pquitslund 2015/05/21 18:14:23 Nit: "any" => 'any' (to stay consistent). More su Nit: "any" => 'any' (to stay consistent). More substantially, is `any` perhaps too inclusive? Or do we really feel like that's safe? Lasse Reichstein Nielsen 2015/05/21 18:30:22 TBH, I just put in "any" to get it to work. I have TBH, I just put in "any" to get it to work. I have no idea what the available versions are, and I hadn't gotten around to checking :) I should just see which version I got in the lock file and request that. pquitslund 2015/05/21 18:38:33 :) Or just leave it as any for now and we can tig Show quoted text On 2015/05/21 18:30:22, Lasse Reichstein Nielsen wrote: > TBH, I just put in "any" to get it to work. I have no idea what the available > versions are, and I hadn't gotten around to checking :) > I should just see which version I got in the lock file and request that. :) Or just leave it as any for now and we can tighten it moving forward. The trick is to make sure that whatever constraints we settle on play nice with what we have in third_party/pkg. Incidentally, I think we'll need to get charcode into third_party before this can be used in the SDK. Do you have plans to make that repo public? Lasse Reichstein Nielsen 2015/05/21 19:10:04 I didn't have any prior plan to do that, it's safe Show quoted text On 2015/05/21 18:38:33, pquitslund wrote: > Incidentally, I think we'll need to get charcode > into third_party before this can be used in the SDK. Do you have plans to make > that repo public? I didn't have any prior plan to do that, it's safely tugged away in an internal repository, but I guess there's no hurt in making it public.
	14

10 dev_dependencies:	15 dev_dependencies:

11 test: '>=0.12.0 <0.13.0'	16 test: '>=0.12.0 <0.13.0'

OLD	NEW

« lib/src/util.dart ('K') | « pubspec.lock ('k') | test/all.dart » ('j') | no next file with comments »