deploy: d141188

Author: epage

print.html

@@ -1423,31 +1423,31 @@ <h2 id="what-to-test"><a class="header" href="#what-to-test">What to test?</a></
 it is time to package and release it!</p>
 <p>There are a few approaches,
 and we’ll look at three of them
-from “quickest to set up” to “most convenient for users”.</p>
+from quickest to set up to most convenient for users.</p>
 <h2 id="quickest-cargo-publish"><a class="header" href="#quickest-cargo-publish">Quickest: <code>cargo publish</code></a></h2>
 <p>The easiest way to publish your app is with cargo.
 Do you remember how we added external dependencies to our project?
-Cargo downloaded them from its default “crate registry”, <a href="https://crates.io/">crates.io</a>.
+Cargo downloaded them from its default crate registry: <a href="https://crates.io/">crates.io</a>.
 With <code>cargo publish</code>,
-you too can publish crates to <a href="https://crates.io/">crates.io</a>.
-And this works for all crates,
+you can publish crates to <a href="https://crates.io/">crates.io</a>,
+and this works for all crates,
 including those with binary targets.</p>
-<p>Publishing a crate to <a href="https://crates.io/">crates.io</a> is pretty straightforward:
-If you haven’t already, create an account on <a href="https://crates.io/">crates.io</a>.
-Currently, this is done via authorizing you on GitHub,
+<p>Publishing a crate to <a href="https://crates.io/">crates.io</a> can be done in a few steps.
+First, if you haven’t already, create an account on <a href="https://crates.io/">crates.io</a>,
+which is done by authorizing you on GitHub,
 so you’ll need to have a GitHub account
-(and be logged in there).
-Next, you log in using cargo on your local machine.
+and be logged in there.
+Second, you log in using cargo on your local machine.
 For that, go to your
 <a href="https://crates.io/me">crates.io account page</a>,
 create a new token,
-and then run <code>cargo login &lt;your-new-token&gt;</code>.
+and run <code>cargo login &lt;your-new-token&gt;</code>.
 You only need to do this once per computer.
 You can learn more about this
 in cargo’s <a href="https://doc.rust-lang.org/1.39.0/cargo/reference/publishing.html">publishing guide</a>.</p>
-<p>Now that cargo as well as crates.io know you,
+<p>Now that cargo and crates.io know you,
 you are ready to publish crates.
-Before you hastily go ahead and publish a new crate (version),
+Before you hastily go ahead and publish a new crate version,
 it’s a good idea to open your <code>Cargo.toml</code> once more
 and make sure you added the necessary metadata.
 You can find all the possible fields you can set
@@ -1469,57 +1469,57 @@ <h2 id="quickest-cargo-publish"><a class="header" href="#quickest-cargo-publish"
 <p><strong>Note:</strong>
 This example includes the mandatory license field
 with a common choice for Rust projects:
-The same license that is also used for the compiler itself.
+The same license that is used for the compiler itself.
 It also refers to a <code>README.md</code> file.
-It should include a quick description of what your project is about,
+It should include a quick description of what your project is about
 and will be included not only on the crates.io page of your crate,
-but also what GitHub shows by default on repository pages.</p>
+but GitHub shows it by default on repository pages.</p>
 </aside>
 <h3 id="how-to-install-a-binary-from-cratesio"><a class="header" href="#how-to-install-a-binary-from-cratesio">How to install a binary from crates.io</a></h3>
 <p>We’ve seen how to publish a crate to crates.io,
 and you might be wondering how to install it.
 In contrast to libraries,
 which cargo will download and compile for you
-when you run <code>cargo build</code> (or a similar command),
+when you run <code>cargo build</code> or a similar command,
 you’ll need to tell it to explicitly install binaries.</p>
 <p>This is done using
 <code>cargo install &lt;crate-name&gt;</code>.
-It will by default download the crate,
+It will download the crate by default,
 compile all the binary targets it contains
 (in “release” mode, so it might take a while)
 and copy them into the <code>~/.cargo/bin/</code> directory.
-(Make sure that your shell knows to look there for binaries!)</p>
+Make sure that your shell knows to look there for binaries!</p>
 <p>It’s also possible to
 install crates from git repositories,
 only install specific binaries of a crate,
 and specify an alternative directory to install them to.
 Have a look at <code>cargo install --help</code> for details.</p>
 <h3 id="when-to-use-it"><a class="header" href="#when-to-use-it">When to use it</a></h3>
 <p><code>cargo install</code> is a simple way to install a binary crate.
-It’s very convenient for Rust developers to use,
+It’s very convenient for Rust developers to use
 but has some significant downsides:
 Since it will always compile your source from scratch,
 users of your tool will need to have
-Rust, cargo, and all other system dependencies your project requires
-to be installed on their machine.
-Compiling large Rust codebases can also take some time.</p>
+Rust, cargo, and all other system dependencies that your project requires
+installed on their machine.
+Compiling large Rust codebases can take some time.</p>
 <p>It’s best to use this for distributing tools
 that are targeted at other Rust developers.
-For example:
-A lot of cargo subcommands
+For example,
+a lot of cargo subcommands
 like <code>cargo-tree</code> or <code>cargo-outdated</code>
 can be installed with it.</p>
 <h2 id="distributing-binaries"><a class="header" href="#distributing-binaries">Distributing binaries</a></h2>
 <p>Rust is a language that compiles to native code
-and by default statically links all dependencies.
+and statically links all dependencies by default.
 When you run <code>cargo build</code>
 on your project that contains a binary called <code>grrs</code>,
 you’ll end up with a binary file called <code>grrs</code>.
-Try it out:
+Try it out!
 Using <code>cargo build</code>, it’ll be <code>target/debug/grrs</code>,
 and when you run <code>cargo build --release</code>, it’ll be <code>target/release/grrs</code>.
 Unless you use crates
-that explicitly need external libraries to be installed on the target system
+that explicitly need external libraries installed on the target system
 (like using the system’s version of OpenSSL),
 this binary will only depend on common system libraries.
 That means,
@@ -1531,61 +1531,61 @@ <h2 id="distributing-binaries"><a class="header" href="#distributing-binaries">D
 There is no need to have Rust installed on the user’s machine,
 and instead of it taking a minute to compile,
 they can instantly run the binary.</p>
-<p>So, as we’ve seen,
+<p>As we’ve seen,
 <code>cargo build</code> <em>already</em> builds binaries for us.
-The only issue is,
+The issue is that
 those are not guaranteed to work on all platforms.
 If you run <code>cargo build</code> on your Windows machine,
 you won’t get a binary that works on a Mac by default.
 Is there a way to generate these binaries
-for all the interesting platforms
+for all of the target platforms
 automatically?</p>
 <h3 id="building-binary-releases-on-ci"><a class="header" href="#building-binary-releases-on-ci">Building binary releases on CI</a></h3>
 <p>If your tool is open sourced
 and hosted on GitHub,
 it’s quite easy to set up a free CI (continuous integration) service
 like <a href="https://travis-ci.com/">Travis CI</a>.
-(There are other services that also work on other platforms, but Travis is very popular.)
-This basically runs setup commands
+There are other services that offer this functionality, but Travis is very popular.
+This runs setup commands
 in a virtual machine
 each time you push changes to your repository.
 What those commands are,
 and the types of machines they run on,
 is configurable.
-For example:
-A good idea is to run <code>cargo test</code>
+For example,
+a good idea is to run <code>cargo test</code>
 on a machine with Rust and some common build tools installed.
 If this fails,
 you know there are issues in the most recent changes.</p>
 <p>We can also use this
 to build binaries and upload them to GitHub!
-Indeed, if we run
+If we run
 <code>cargo build --release</code>
 and upload the binary somewhere,
 we should be all set, right?
 Not quite.
 We still need to make sure the binaries we build
 are compatible with as many systems as possible.
 For example,
-on Linux we can compile not for the current system,
-but instead for the <code>x86_64-unknown-linux-musl</code> target,
-to not depend on default system libraries.
+on Linux we can compile for the current system
+or the <code>x86_64-unknown-linux-musl</code> target and
+not depend on default system libraries.
 On macOS, we can set <code>MACOSX_DEPLOYMENT_TARGET</code> to <code>10.7</code>
 to only depend on system features present in versions 10.7 and older.</p>
 <p>You can see one example of building binaries using this approach
 <a href="https://github.com/rustwasm/wasm-pack/blob/51e6351c28fbd40745719e6d4a7bf26dadd30c85/.travis.yml#L74-L91">here</a> for Linux and macOS
-and <a href="https://github.com/rustwasm/wasm-pack/blob/51e6351c28fbd40745719e6d4a7bf26dadd30c85/.appveyor.yml">here</a> for Windows (using AppVeyor).</p>
-<p>Another way is to use pre-built (Docker) images
+and <a href="https://github.com/rustwasm/wasm-pack/blob/51e6351c28fbd40745719e6d4a7bf26dadd30c85/.appveyor.yml">here</a> for Windows using AppVeyor.</p>
+<p>Another way is to use pre-built (i.e. Docker) images
 that contain all the tools we need
 to build binaries.
-This allows us to easily target more exotic platforms, too.
+This allows us to easily target more exotic platforms as well.
 The <a href="https://github.com/japaric/trust">trust</a> project contains
 scripts that you can include in your project
-as well as instructions on how to set this up.
+and instructions on how to set this up.
 It also includes support for Windows using AppVeyor.</p>
 <p>If you’d rather set this up locally
 and generate the release files on your own machine,
-still have a look at trust.
+have a look at <a href="https://github.com/japaric/trust">trust</a>.
 It uses <a href="https://github.com/rust-embedded/cross">cross</a> internally,
 which works similar to cargo
 but forwards commands to a cargo process inside a Docker container.
@@ -1595,48 +1595,47 @@ <h3 id="how-to-install-these-binaries"><a class="header" href="#how-to-install-t
 <p>You point your users to your release page
 that might look something <a href="https://github.com/rustwasm/wasm-pack/releases/tag/v0.5.1">like this one</a>,
 and they can download the artifacts we’ve just created.
-The release artifacts we’ve just generated are nothing special:
-At the end, they are just archive files that contain our binaries!
+The release artifacts we’ve generated are nothing special.
+They are just archive files that contain our binaries!
 This means that users of your tool
 can download them with their browser,
-extract them (often happens automatically),
+extract them (often automatically),
 and copy the binaries to a place they like.</p>
-<p>This does require some experience with manually “installing” programs,
+<p>This does require some experience with manually installing programs,
 so you want to add a section to your README file
 on how to install this program.</p>
 <aside class="note">
 <p><strong>Note:</strong>
-If you used <a href="https://github.com/japaric/trust">trust</a> to build your binaries and added them to GitHub releases,
+If you use <a href="https://github.com/japaric/trust">trust</a> to build your binaries and add them to GitHub releases,
 you can also tell people to run
 <code>curl -LSfs https://japaric.github.io/trust/install.sh | sh -s -- --git your-name/repo-name</code>
 if you think that makes it easier.</p>
 </aside>
 <h3 id="when-to-use-it-1"><a class="header" href="#when-to-use-it-1">When to use it</a></h3>
-<p>Having binary releases is a good idea in general,
-there’s hardly any downside to it.
+<p>Having binary releases is a good idea in general.
+There’s hardly any downside to it.
 It does not solve the problem of users having to manually
 install and update
 your tools,
-but they can quickly get the latest releases version
+but they can quickly get the latest release’s version
 without the need to install Rust.</p>
 <h3 id="what-to-package-in-addition-to-your-binaries"><a class="header" href="#what-to-package-in-addition-to-your-binaries">What to package in addition to your binaries</a></h3>
 <p>Right now,
 when a user downloads our release builds,
 they will get a <code>.tar.gz</code> file
 that only contains binary files.
-So, in our example project,
-they will just get a single <code>grrs</code> file they can run.
-But there are some more files we already have in our repository
+In our example project,
+they will just get a single <code>grrs</code> file they can run,
+but there are more files we already have in our repository
 that they might want to have.
-The README file that tells them how to use this tool,
+The README file that tells them how to use this tool
 and the license file(s),
 for example.
 Since we already have them,
 they are easy to add.</p>
-<p>There are some more interesting files
-that make sense especially for command-line tools,
-though:
-How about we also ship a man page in addition to that README file,
+<p>There are more interesting files
+that make sense, especially for command-line tools.
+How about we ship a man page in addition to that README file
 and config files that add completions of the possible flags to your shell?
 You can write these by hand,
 but <em>clap</em>, the argument parsing library we use
@@ -1646,21 +1645,21 @@ <h3 id="what-to-package-in-addition-to-your-binaries"><a class="header" href="#w
 for more details.</p>
 <h2 id="getting-your-app-into-package-repositories"><a class="header" href="#getting-your-app-into-package-repositories">Getting your app into package repositories</a></h2>
 <p>Both approaches we’ve seen so far
-are not how you typically install software on your machine.
-Especially command-line tools
+are not how you typically install software on your machine,
+especially for command-line tools that
 you install using global package managers
 on most operating systems.
 The advantages for users are quite obvious:
-There is no need to think about how to install your program,
-if it can be installed the same way as they install the other tools.
+There is no need to think about how to install your program
+if it can be installed the same way as they install other tools.
 These package managers also allow users to update their programs
 when a new version is available.</p>
 <p>Sadly, supporting different systems means
 you’ll have to look at how these different systems work.
 For some,
 it might be as easy as adding a file to your repository
 (e.g. adding a Formula file like <a href="https://github.com/BurntSushi/ripgrep/blob/31adff6f3c4bfefc9e77df40871f2989443e6827/pkg/brew/ripgrep-bin.rb">this</a> for macOS’s <code>brew</code>),
-but for others you’ll often need to send in patches yourself
+but for others, you’ll often need to send in patches yourself
 and add your tool to their repositories.
 There are helpful tools like
 <a href="https://crates.io/crates/cargo-bundle">cargo-bundle</a>,
@@ -1676,16 +1675,16 @@ <h3 id="an-example-ripgrep"><a class="header" href="#an-example-ripgrep">An exam
 <p><a href="https://github.com/BurntSushi/ripgrep">ripgrep</a> is an alternative to <code>grep</code>/<code>ack</code>/<code>ag</code> and is written in Rust.
 It’s quite successful and is packaged for many operating systems:
 Just look at <a href="https://github.com/BurntSushi/ripgrep/tree/31adff6f3c4bfefc9e77df40871f2989443e6827#installation">the “Installation” section</a> of its README!</p>
-<p>Note that it lists a few different options how you can install it:
-It starts with a link to the GitHub releases
-which contain the binaries so you can download them directly;
-then it lists how to install it using a bunch of different package managers;
-finally, you can also install it using <code>cargo install</code>.</p>
-<p>This seems like a very good idea:
-Don’t pick and choose one of the approaches presented here,
-but start with <code>cargo install</code>,
-add binary releases,
-and finally start distributing your tool using system package managers.</p>
+<p>Note that it lists a few different options on how you can install it:
+It starts with a link to the GitHub releases,
+which contain the binaries so that you can download them directly,
+it lists how to install it using a bunch of different package managers,
+and you can also install it using <code>cargo install</code>.</p>
+<p>This seems like a very good idea.
+Don’t pick and choose one of the approaches presented here.
+Start with <code>cargo install</code>
+and add binary releases
+before finally distributing your tool using system package managers.</p>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="in-depth-topics"><a class="header" href="#in-depth-topics">In-depth topics</a></h1>
 <p>A small collection of chapters covering some more details
 that you might care about when writing your command line application.</p>