Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(712)

Unified Diff: src/site/docs/pub-package-manager/versioning.markdown

Issue 10891023: add a name: and mark it as required (Closed) Base URL: git@github.com:dart-lang/dartlang.org.git@master
Patch Set: tweak to instructions Created 8 years, 4 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 side-by-side diff with in-line comments
Download patch
« no previous file with comments | « src/site/docs/pub-package-manager/pubspec.markdown ('k') | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: src/site/docs/pub-package-manager/versioning.markdown
diff --git a/src/site/docs/pub-package-manager/versioning.markdown b/src/site/docs/pub-package-manager/versioning.markdown
index c38c07cdc8708f3c597607b862ab237f2d238cd6..e31552d3ea362eb7ab253539754bae54c8c09a77 100644
--- a/src/site/docs/pub-package-manager/versioning.markdown
+++ b/src/site/docs/pub-package-manager/versioning.markdown
@@ -219,13 +219,13 @@ I'll walk through an example so you can see what this means. Let's say we have
two apps. Here are their pubspecs:
{% highlight yaml %}
-# myapp
+name: my_app
dependencies:
widgets:
{% endhighlight %}
{% highlight yaml %}
-# otherapp
+name: other_app
dependencies:
widgets:
collections: '<1.5.0'
@@ -234,19 +234,19 @@ dependencies:
They both depend on `widgets`, whose pubspec is:
{% highlight yaml %}
-# widgets
+name: widgets
dependencies:
collections: '>=1.0.0 <2.0.0'
{% endhighlight %}
-The `otherapp` package uses depends directly on `collections` itself. The
+The `other_app` package uses depends directly on `collections` itself. The
interesting part is that it happens to have a different version constraint on
it than `widgets` does.
What this means is that you can't just look at the `widgets` package in
isolation to figure out what version of `collections` it will use. It depends
-on the context. In `myapp`, `widgets` will be using `collections 1.9.9`. But
-in `otherapp`, `widgets` will get saddled with `collections 1.4.9` because of
+on the context. In `my_app`, `widgets` will be using `collections 1.9.9`. But
+in `other_app`, `widgets` will get saddled with `collections 1.4.9` because of
the *other* constraint that `otherapp` places on it.
This is why each app gets its own "packages" directory: The concrete version
@@ -323,24 +323,28 @@ Sometimes this process never settles down into a stable solution. Gaze into
the abyss:
{% highlight yaml %}
-# myapp 0.0.0
+name: my_app
+version: 0.0.0
dependencies:
yin: '>=1.0.0'
{% endhighlight %}
{% highlight yaml %}
-# yin 1.0.0
+name: yin
+version: 1.0.0
dependencies:
{% endhighlight %}
{% highlight yaml %}
-# yin 2.0.0
+name: yin
+version: 2.0.0
dependencies:
yang: '1.0.0'
{% endhighlight %}
{% highlight yaml %}
-# yang 1.0.0
+name: yang
+version: 1.0.0
dependencies:
yin: '1.0.0'
{% endhighlight %}
« no previous file with comments | « src/site/docs/pub-package-manager/pubspec.markdown ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698