We were assuming that all globally-activated packages have a .packages
file, but this isn't true for packages that were activated by earlier
versions of pub.

Closes #1316

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1292003005 .

Since there's no way to load resources without using the packages/
directory, this flag will introduce a lot of confusing unfixable
breakage. We should un-hide it once there's sufficient SDK support for
locating/loading resources (dart-lang/sdk#23990).

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1292933003 .

Previously, if a dependency depended on the entrypoint package, the
entrypoint would have all its direct dependencies re-printed. This fixes
that.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1274763010 .

Previously, several commands automatically ran "pub get" implicitly before doing
their work. We've determined that this behavior is confusing, and for "pub run"
in particular, makes the executables seem much slower than they actually are.

This also allows us to make access to the entrypoint's package graph
synchronous.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1282533003 .

The spec doesn't actually need all the data loaded from the package
graph; all it needs are the locations of packages which can be looked up
using their IDs and a SourceRegistry.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1282083002 .

This also has it store its SourceRegistry, so that various methods don't
need to re-supply it.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1281043004 .

It never really made sense for this to be asynchronous; most sources
didn't even do any IO to determine the directory. The only exception was
the git source, which would actually *clone a repository* if one didn't
exist yet. This heavyweight behavior wasn't a good fit for what looks
like a lightweight method anyway.

Making this synchronous has a ripple effect of making a bunch of other
methods synchronous, too. Hooray for synchrony!

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1276673006 .

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1281623002 .

R=nweiz@google.com

Review URL: https://codereview.chromium.org//1278813003 .

Closes pub#22

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1277773002 .

Fixes #1230.

R=nweiz@google.com

Review URL: https://codereview.chromium.org//1272813003 .

This reverts commit 7fbc1040, which
reverted commit dc626af3.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1272903002 .

Currently we don't auto-run "pub get" if there's no lockfile and also no
dependencies. We should, in order to create a self-link.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1277633004 .

Makes pub serve less spammy when used with Dartium where you have a
slew of requests for each source file.

Review URL: https://codereview.chromium.org//1267023002 .

This reverts commit dc626af3.

This broke due to dart-lang/sdk#23991.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1272833003 .

Previously this was using the packages/ directory, but that's no longer
reliable since there's now an option to not generate it.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1269393003 .

Fixes #1109.

R=nweiz@google.com

Review URL: https://codereview.chromium.org//1267853002 .

Closes #1304

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1248483003 .

It turns out it's not safe to assume that pub is checked out from Git
when running from the SDK repo.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1246713005 .

Now instead of just saying how many packages failed to be
reinstalled/reactivated, "pub cache repair" will print a list of those
packages.

This also fixes an issue where "pub cache repair" would incorrectly
return a 0 exit code when packages failed to reactivate.

Closes #1301

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1239623005 .

This is helpful for subprocesses to be able to spawn Dart with
Platform.executableArguments and have that work regardless of the
working directory.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1236973002 .

If a package used two instances of its own transformer on the
transformer's own file (or a file it imported), the dependency computer
would crash.

Closes #1298

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1229303004 .

This causes a substantial amount of pain, and doesn't seem to really
help anyone. It's rare to have the connection with the server go
completely dead without actually closing.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1235013002 .

This will help avoid issues like #1294 in the future.

R=rnystrom@google.com, rnystrom@gmail.com

Review URL: https://codereview.chromium.org//1227913009 .

* forward_signal_posix_test needed to be marked as incompatible with
  Windows.

* Deleting the sandbox directory would sometimes fail due to locking
  issues, and this failure would obscure underlying issues.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1226083002 .

Closes #1296

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1233533002 .

* Normalize paths before they're passed to dart2js. It handles "." and
  ".." path components poorly.

* Ensure that paths emitted by list-package-dirs are always absolute and
  normalized for backwards-compatibility with the existing protocol.

* Make Package.listFiles work for an in-memory package.

* Fix an error message expectation in packages_file_test.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1228683003 .

It can choke on relative paths in surprising ways.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1231893004 .

* The package spec's reference to the entrypoint package was pointing to
  the hosted cache rather than the package's directory. This was caused
  by the package graph's instance of the entrypoint package incorrectly
  pointing to the cache; the graph now re-uses `entrypoint.root`.

* The package spec didn't contain relative paths for relative path
  dependencies. This was being missed by our tests because the package
  spec parser was automatically converting all paths to absolute at
  parse-time.

Closes #1294

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1228093003 .

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1224153002 .

* Some HTTP requests were still being made. These are now avoided, and
  the tests have been modified to assert that no HTTP requests are made
  at all.

* When a specific package version was in a package's lockfile *and*
  available on the server but wasn't in the user's cache, pub would
  crash when run in offline mode.

Closes #1293

Print a nice error for missing offline packages.

Previously, this would print an unhelpful message along with "this is an
unexpected error".

Closes #1293

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1226133003 .

OS X symlinks its /tmp directory, so we need to resolve symlinks before
we can safely compare paths that might include /tmp.

Review URL: https://codereview.chromium.org//1225483003.

Update README.md

When a package both transformed itself and had a dev transformer (that
is, a transformer that only runs on non-public files), *and* that
package's self-transformed code was imported by another transformer, the
dependency computer could return the dev transformer in its results.

Closes #1290
Closes #1291

R=kevmoo@google.com

Review URL: https://codereview.chromium.org//1220223008.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1217943009.

Somehow I didn't notice that the test I added for this wasn't actually
passing.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1211243009.

I forgot to update the --help output here.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1220543006.

Now that pub uses the new test runner, some of its logic for running in
the Dart SDK repository needs to be updated.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1216163002.

When running an executable directly from the filesystem, "pub run" would
sometimes fail to give it the correct package root.

R=rnystrom@google.com

Review URL: https://codereview.chromium.org//1217923002.