Revert "Support relative paths in path dependencies."

utils/pub/source.dart

Index: utils/pub/source.dart
diff --git a/utils/pub/source.dart b/utils/pub/source.dart
index 0568d95740cb1e2fd3ce687cf05b40191a9f276f..1fd93271282a4f9412aead2e1b28675386aa4d0d 100644
--- a/utils/pub/source.dart
+++ b/utils/pub/source.dart
@@ -169,23 +169,13 @@ abstract class Source {
   /// When a [Pubspec] or [LockFile] is parsed, it reads in the description for
   /// each dependency. It is up to the dependency's [Source] to determine how
   /// that should be interpreted. This will be called during parsing to validate
-  /// that the given [description] is well-formed according to this source, and
-  /// to give the source a chance to canonicalize the description.
-  ///
-  /// [containingPath] is the path to the local file (pubspec or lockfile)
-  /// where this description appears. It may be `null` if the description is
-  /// coming from some in-memory source (such as pulling down a pubspec from
-  /// pub.dartlang.org).
-  ///
-  /// It should return if a (possibly modified) valid description, or throw a
-  /// [FormatException] if not valid.
+  /// that the given [description] is well-formed according to this source. It
+  /// should return if the description is valid, or throw a [FormatException] if
+  /// not.
   ///
   /// [fromLockFile] is true when the description comes from a [LockFile], to
   /// allow the source to use lockfile-specific descriptions via [resolveId].
-  dynamic parseDescription(String containingPath, description,
-                           {bool fromLockFile: false}) {
-    return description;
-  }
+  void validateDescription(description, {bool fromLockFile: false}) {}
 
   /// Returns whether or not [description1] describes the same package as
   /// [description2] for this source. This method should be light-weight. It
@@ -209,7 +199,7 @@ abstract class Source {
   /// the resolved id.
   ///
   /// The returned [PackageId] may have a description field that's invalid
-  /// according to [parseDescription], although it must still be serializable
+  /// according to [validateDescription], although it must still be serializable
   /// to JSON and YAML. It must also be equal to [id] according to
   /// [descriptionsEqual].
   ///