pkg: analysis aided cleanup

pkg/path/pubspec.yaml

Index: pkg/path/pubspec.yaml
diff --git a/pkg/path/pubspec.yaml b/pkg/path/pubspec.yaml
index 35047ac2e7221133c5984e657570d41fe6c84854..a3661220ff617f2fb226a7904ea1c7653850f07a 100644
--- a/pkg/path/pubspec.yaml
+++ b/pkg/path/pubspec.yaml
@@ -1,8 +1,10 @@
 name: path
-author: "Dart Team <misc@dartlang.org>"
-homepage: http://www.dartlang.org
-documentation: http://api.dartlang.org/docs/pkg/path
+author: Dart Team <misc@dartlang.org>
 description: >
  A string-based path manipulation library. All of the path operations you know
  and love, with solid support on both Windows and POSIX (Linux and Mac OS X)
  machines.
+homepage: http://www.dartlang.org
+documentation: http://api.dartlang.org/docs/pkg/path
+dev_dependencies:
+  unittest: any

[gram, 2013/08/05 23:23:12]

Do we need this unittest dependency here?

I'm not sure what the right convention should be. Personally I favor putting a
pubspec with a unittest dependency in the test directory, and not having it in
the main package directory; that means you can open up the test directory in the
editor and run the tests after a pub install, and if you're just using a package
and not testing it you don't need the dependency here.

Bob, Nathan, do you have an opinion here? Should unittest go in as a dependency
of all pub packages with tests in their top-level pubspecs?