OpenE2K/rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

clarify that rust_pkg is a place-holder

Browse Source 
the switch from package `hello` to `rust_pkg` is a little jarring; I'd use <var> but I don't see how. ALL_CAPS seems like a reasonable  poor-man's <var>.
This commit is contained in:
Dan Connolly 2013-09-30 22:57:09 -05:00
parent bc6dd906a9
commit 398e2c479a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/tutorial-rustpkg.md
View File

@ -35,11 +35,11 @@ This makes sense, as we haven't gotten it from anywhere yet! Luckily for us,
used like this:
~~~ {.notrust}
$ rustpkg install pkg_id
$ rustpkg install PKG_ID
~~~
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
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
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
build your own `hello` library if you want, and that's fine. We'd both host