auto merge of #9645 : dckc/rust/patch-2, r=catamorphism
the switch from package `hello` to `pkg_id` is a little jarring; I'd use `<var>` but I don't see how. ALL_CAPS i.e. PKG_ID seems like a reasonable poor-man's `<var>`.
This commit is contained in:
commit
320af9b157
|
@ -35,11 +35,11 @@ This makes sense, as we haven't gotten it from anywhere yet! Luckily for us,
|
||||||
used like this:
|
used like this:
|
||||||
|
|
||||||
~~~ {.notrust}
|
~~~ {.notrust}
|
||||||
$ rustpkg install pkg_id
|
$ rustpkg install PKG_ID
|
||||||
~~~
|
~~~
|
||||||
|
|
||||||
This will install a package named 'pkg_id' into your current Rust environment.
|
This will install a package named `PKG_ID` into your current Rust environment.
|
||||||
I called it 'pkg_id' in this example because `rustpkg` calls this a 'package
|
I called it `PKG_ID` in this example because `rustpkg` calls this a 'package
|
||||||
identifier.' When using it with an external package like this, it's often a
|
identifier.' When using it with an external package like this, it's often a
|
||||||
URI fragment. You see, Rust has no central authority for packages. You can
|
URI fragment. You see, Rust has no central authority for packages. You can
|
||||||
build your own `hello` library if you want, and that's fine. We'd both host
|
build your own `hello` library if you want, and that's fine. We'd both host
|
||||||
|
|
Loading…
Reference in New Issue