Change the deferred library check tool to allow unspecified packages to be in

README.md

Index: README.md
diff --git a/README.md b/README.md
index 524a38b8286352a65dee6a1d2c0f752e5961e96c..ffc1ce885ec180b1a57042e5b9ba9d7ad9a0d305 100644
--- a/README.md
+++ b/README.md
@@ -207,32 +207,38 @@ The format of the YAML file is:
 
 ```yaml
 main:
-  packages:
+  include:
     - some_package

[Siggi Cherem (dart-lang), 2015/12/18 02:29:41]

I like that the new syntax allows you to extend this to support libraries
without a breaking change. You would be able to say that if the item is an
identifier it is the name of the package, but if it's a URI, it is the specific
library with that uri.

[Harry Terkelsen, 2015/12/18 21:22:21]

Right, we can add that when customers want to check at the library level.

     - other_package
+  exclude:
+    - some_other_package
 
 foo:
-  packages:
+  include:
     - foo
     - bar
 
 baz:
-  packages:
+  include:
     - baz
     - quux
+  exclude:
+    - zardoz
 ```
 
 The YAML file consists of a list of declarations, one for each deferred
 part expected in the output. At least one of these parts must be named
 "main"; this is the main part that contains the program entrypoint. Each
 top-level part contains a list of package names that are expected to be
-contained in that part. Any package that is not explicitly listed is
-expected to be in the main part. For instance, in the example YAML above
-the part named "baz" is expected to contain the packages "baz" and "quux".
+contained in that part, a list of package names that are expected to be in
+another part, or both. For instance, in the example YAML above the part named
+"baz" is expected to contain the packages "baz" and "quux" and exclude the
+package "zardoz".
 
 The names for parts given in the specification YAML file (besides "main")
-are arbitrary and just used for reporting when the output does not meet the
-specification.
+are the same as the name given to the deferred import in the dart file. For
+instance, if you have `import 'package:foo/foo.dart' deferred as foo;` in your

[Siggi Cherem (dart-lang), 2015/12/18 02:29:41]

to make it less ambiguous, it might be worth changing this example to:

`import 'package:foo/bar.dart' deferred as baz`

Or:
`import 'package:pkg/lib.dart' deferred as prefix` and say to use 'pkg'

[Harry Terkelsen, 2015/12/18 21:22:21]

It's actually the other way. The part after 'as' is the name of the part.
Otherwise, there is no way to defer import 2 different libraries in the same
package. This is also the way that I see customers naturally naming their parts
in the spec file

[Siggi Cherem (dart-lang), 2015/12/18 21:34:25]

I see, thanks for clarifying, that's nice, for some reason I thought we didn't
have that info in dump-info

+dart file, then the corresponding name in the specification file is 'foo'.
 
 ### Function size analysis tool