Auto merge of #6066 - zachlute:project-to-package-docs, r=alexcrichton

Replaced 'project' with 'package' in Cargo documentation.

Partial fix for #6056.

I tried to make a distinction between places that were talking about Cargo 'projects' vs. a generic concept of a 'project' or a github 'project'. It's entirely possible I was overzealous, so please tell me if some of these changes look dumb.

Author: bors

src/doc/src/SUMMARY.md

@@ -8,10 +8,10 @@
 
 * [Cargo Guide](guide/index.md)
     * [Why Cargo Exists](guide/why-cargo-exists.md)
-    * [Creating a New Project](guide/creating-a-new-project.md)
-    * [Working on an Existing Project](guide/working-on-an-existing-project.md)
+    * [Creating a New Package](guide/creating-a-new-project.md)
+    * [Working on an Existing Package](guide/working-on-an-existing-project.md)
     * [Dependencies](guide/dependencies.md)
-    * [Project Layout](guide/project-layout.md)
+    * [Package Layout](guide/project-layout.md)
     * [Cargo.toml vs Cargo.lock](guide/cargo-toml-vs-cargo-lock.md)
     * [Tests](guide/tests.md)
     * [Continuous Integration](guide/continuous-integration.md)

src/doc/src/faq.md

@@ -13,7 +13,7 @@ even when people use the registry as the primary source of packages.
 
 We think that it’s very important to support multiple ways to download
 packages, including downloading from GitHub and copying packages into
-your project itself.
+your package itself.
 
 That said, we think that [crates.io] offers a number of important benefits, and
 will likely become the primary way that people download packages in Cargo.
@@ -46,7 +46,7 @@ languages include:
 
 Yes!
 
-Cargo handles compiling Rust code, but we know that many Rust projects
+Cargo handles compiling Rust code, but we know that many Rust packages
 link against C code. We also know that there are decades of tooling
 built up around compiling languages other than Rust.
 
@@ -58,7 +58,7 @@ functionality among packages.
 ### Can Cargo be used inside of `make` (or `ninja`, or ...)
 
 Indeed. While we intend Cargo to be useful as a standalone way to
-compile Rust projects at the top-level, we know that some people will
+compile Rust packages at the top-level, we know that some people will
 want to invoke Cargo from other build tools.
 
 We have designed Cargo to work well in those contexts, paying attention
@@ -67,7 +67,7 @@ have some work to do on those fronts, but using Cargo in the context of
 conventional scripts is something we designed for from the beginning and
 will continue to prioritize.
 
-### Does Cargo handle multi-platform projects or cross-compilation?
+### Does Cargo handle multi-platform packages or cross-compilation?
 
 Rust itself provides facilities for configuring sections of code based
 on the platform. Cargo also supports [platform-specific
@@ -77,7 +77,7 @@ configuration in `Cargo.toml` in the future.
 [target-deps]: reference/specifying-dependencies.html#platform-specific-dependencies
 
 In the longer-term, we’re looking at ways to conveniently cross-compile
-projects using Cargo.
+packages using Cargo.
 
 ### Does Cargo support environments, like `production` or `test`?
 
@@ -105,10 +105,10 @@ issue][3].
 
 The purpose of a `Cargo.lock` is to describe the state of the world at the time
 of a successful build. It is then used to provide deterministic builds across
-whatever machine is building the project by ensuring that the exact same
+whatever machine is building the package by ensuring that the exact same
 dependencies are being compiled.
 
-This property is most desirable from applications and projects which are at the
+This property is most desirable from applications and packages which are at the
 very end of the dependency chain (binaries). As a result, it is recommended that
 all binaries check in their `Cargo.lock`.
 

src/doc/src/getting-started/first-steps.md

@@ -1,6 +1,6 @@
 ## First Steps with Cargo
 
-To start a new project with Cargo, use `cargo new`:
+To start a new package with Cargo, use `cargo new`:
 
 ```console
 $ cargo new hello_world
@@ -32,7 +32,7 @@ authors = ["Your Name <[email protected]>"]
 ```
 
 This is called a **manifest**, and it contains all of the metadata that Cargo
-needs to compile your project.
+needs to compile your package.
 
 Here’s what’s in `src/main.rs`:
 
@@ -46,7 +46,7 @@ Cargo generated a “hello world” for us. Let’s compile it:
 
 ```console
 $ cargo build
-   Compiling hello_world v0.1.0 (file:///path/to/project/hello_world)
+   Compiling hello_world v0.1.0 (file:///path/to/package/hello_world)
 ```
 
 And then run it:
@@ -60,7 +60,7 @@ We can also use `cargo run` to compile and then run it, all in one step:
 
 ```console
 $ cargo run
-     Fresh hello_world v0.1.0 (file:///path/to/project/hello_world)
+     Fresh hello_world v0.1.0 (file:///path/to/package/hello_world)
    Running `target/hello_world`
 Hello, world!
 ```

src/doc/src/guide/cargo-toml-vs-cargo-lock.md

@@ -8,7 +8,7 @@ about them, here’s a summary:
 * `Cargo.lock` contains exact information about your dependencies. It is
   maintained by Cargo and should not be manually edited.
 
-If you’re building a library that other projects will depend on, put
+If you’re building a library that other packages will depend on, put
 `Cargo.lock` in your `.gitignore`. If you’re building an executable like a
 command-line tool or an application, check `Cargo.lock` into `git`. If you're
 curious about why that is, see ["Why do binaries have `Cargo.lock` in version
@@ -18,8 +18,8 @@ FAQ](faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-librarie
 Let’s dig in a little bit more.
 
 `Cargo.toml` is a **manifest** file in which we can specify a bunch of
-different metadata about our project. For example, we can say that we depend
-on another project:
+different metadata about our package. For example, we can say that we depend
+on another package:
 
 ```toml
 [package]
@@ -31,13 +31,13 @@ authors = ["Your Name <[email protected]>"]
 rand = { git = "https://github.com/rust-lang-nursery/rand.git" }
 ```
 
-This project has a single dependency, on the `rand` library. We’ve stated in
+This package has a single dependency, on the `rand` library. We’ve stated in
 this case that we’re relying on a particular Git repository that lives on
 GitHub. Since we haven’t specified any other information, Cargo assumes that
-we intend to use the latest commit on the `master` branch to build our project.
+we intend to use the latest commit on the `master` branch to build our package.
 
-Sound good? Well, there’s one problem: If you build this project today, and
-then you send a copy to me, and I build this project tomorrow, something bad
+Sound good? Well, there’s one problem: If you build this package today, and
+then you send a copy to me, and I build this package tomorrow, something bad
 could happen. There could be more commits to `rand` in the meantime, and my
 build would include new commits while yours would not. Therefore, we would
 get different builds. This would be bad because we want reproducible builds.
@@ -85,7 +85,7 @@ source = "git+https://github.com/rust-lang-nursery/rand.git#9f35b8e439eeedd60b94
 ```
 
 You can see that there’s a lot more information here, including the exact
-revision we used to build. Now when you give your project to someone else,
+revision we used to build. Now when you give your package to someone else,
 they’ll use the exact same SHA, even though we didn’t specify it in our
 `Cargo.toml`.
 

src/doc/src/guide/continuous-integration.md

@@ -2,7 +2,7 @@
 
 ### Travis CI
 
-To test your project on Travis CI, here is a sample `.travis.yml` file:
+To test your package on Travis CI, here is a sample `.travis.yml` file:
 
 ```yaml
 language: rust
@@ -22,7 +22,7 @@ information.
 
 ### GitLab CI
 
-To test your project on GitLab CI, here is a sample `.gitlab-ci.yml` file:
+To test your package on GitLab CI, here is a sample `.gitlab-ci.yml` file:
 
 ```yaml
 stages:

src/doc/src/guide/creating-a-new-project.md

@@ -1,6 +1,6 @@
-## Creating a New Project
+## Creating a New Package
 
-To start a new project with Cargo, use `cargo new`:
+To start a new package with Cargo, use `cargo new`:
 
 ```console
 $ cargo new hello_world --bin
@@ -33,7 +33,7 @@ authors = ["Your Name <[email protected]>"]
 ```
 
 This is called a **manifest**, and it contains all of the metadata that Cargo
-needs to compile your project.
+needs to compile your package.
 
 Here’s what’s in `src/main.rs`:
 
@@ -47,7 +47,7 @@ Cargo generated a “hello world” for us. Let’s compile it:
 
 ```console
 $ cargo build
-   Compiling hello_world v0.1.0 (file:///path/to/project/hello_world)
+   Compiling hello_world v0.1.0 (file:///path/to/package/hello_world)
 ```
 
 And then run it:
@@ -63,7 +63,7 @@ compiled):
 
 ```console
 $ cargo run
-   Compiling hello_world v0.1.0 (file:///path/to/project/hello_world)
+   Compiling hello_world v0.1.0 (file:///path/to/package/hello_world)
      Running `target/debug/hello_world`
 Hello, world!
 ```
@@ -76,7 +76,7 @@ your files with optimizations turned on:
 
 ```console
 $ cargo build --release
-   Compiling hello_world v0.1.0 (file:///path/to/project/hello_world)
+   Compiling hello_world v0.1.0 (file:///path/to/package/hello_world)
 ```
 
 `cargo build --release` puts the resulting binary in `target/release` instead of

src/doc/src/guide/dependencies.md

@@ -59,7 +59,7 @@ $ cargo build
      Compiling memchr v0.1.5
      Compiling aho-corasick v0.3.0
      Compiling regex v0.1.41
-     Compiling hello_world v0.1.0 (file:///path/to/project/hello_world)
+     Compiling hello_world v0.1.0 (file:///path/to/package/hello_world)
 ```
 
 Our `Cargo.lock` contains the exact information about which revision of all of

src/doc/src/guide/index.md

@@ -1,13 +1,13 @@
 ## Cargo Guide
 
 This guide will give you all that you need to know about how to use Cargo to
-develop Rust projects.
+develop Rust packages.
 
 * [Why Cargo Exists](guide/why-cargo-exists.html)
-* [Creating a New Project](guide/creating-a-new-project.html)
-* [Working on an Existing Cargo Project](guide/working-on-an-existing-project.html)
+* [Creating a New Package](guide/creating-a-new-project.html)
+* [Working on an Existing Cargo Package](guide/working-on-an-existing-project.html)
 * [Dependencies](guide/dependencies.html)
-* [Project Layout](guide/project-layout.html)
+* [Package Layout](guide/project-layout.html)
 * [Cargo.toml vs Cargo.lock](guide/cargo-toml-vs-cargo-lock.html)
 * [Tests](guide/tests.html)
 * [Continuous Integration](guide/continuous-integration.html)

src/doc/src/guide/project-layout.md

@@ -1,7 +1,7 @@
-## Project Layout
+## Package Layout
 
 Cargo uses conventions for file placement to make it easy to dive into a new
-Cargo project:
+Cargo package:
 
 ```
 .
@@ -20,7 +20,7 @@ Cargo project:
     └── some-integration-tests.rs
 ```
 
-* `Cargo.toml` and `Cargo.lock` are stored in the root of your project (*package
+* `Cargo.toml` and `Cargo.lock` are stored in the root of your package (*package
   root*).
 * Source code goes in the `src` directory.
 * The default library file is `src/lib.rs`.

src/doc/src/guide/tests.md

@@ -6,21 +6,21 @@ Tests in your `src` files should be unit tests, and tests in `tests/` should be
 integration-style tests. As such, you’ll need to import your crates into
 the files in `tests`.
 
-Here's an example of running `cargo test` in our project, which currently has
+Here's an example of running `cargo test` in our package, which currently has
 no tests:
 
 ```console
 $ cargo test
    Compiling rand v0.1.0 (https://github.com/rust-lang-nursery/rand.git#9f35b8e)
-   Compiling hello_world v0.1.0 (file:///path/to/project/hello_world)
+   Compiling hello_world v0.1.0 (file:///path/to/package/hello_world)
      Running target/test/hello_world-9c2b65bbb79eabce
 
 running 0 tests
 
 test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
 ```
 
-If our project had tests, we would see more output with the correct number of
+If our package had tests, we would see more output with the correct number of
 tests.
 
 You can also run a specific test by passing a filter: