More build-manifest docs

[rust.git] / src / tools / build-manifest / README.md

diff --git a/src/tools/build-manifest/README.md b/src/tools/build-manifest/README.md
index 40dce38742a14443d722d209038d4ffb56b92f29..9d30c554186be1f6bd109170f1adbc07f8846502 100644 (file)
--- a/src/tools/build-manifest/README.md
+++ b/src/tools/build-manifest/README.md
@@ -8,10 +8,9 @@ This gets called by `promote-release` <https://github.com/rust-lang/promote-rele
 
 ## Adding a new component
 
-There are several steps involved here.
 1. Add a new `Step` to `dist.rs`. This should usually be named after the filename of the uploaded tarball. See https://github.com/rust-lang/rust/pull/101799/files#diff-2c56335faa24486df09ba392d8900c57e2fac4633e1f7038469bcf9ed3feb871 for an example.
     a. If appropriate, call `tarball.is_preview(true)` for the component.
-3. Add a new `PkgType` to build-manifest. Fix all the compile errors as appropriate.
+2. Add a new `PkgType` to build-manifest. Fix all the compile errors as appropriate.
 
 ## Testing changes locally
 
@@ -30,5 +29,5 @@ Then, you can generate the manifest and all the packages from `build/dist` to
 
 ```sh
 mkdir -p build/manifest
-cargo +nightly run -p build-manifest build/dist build/manifest 1970-01-01 http://example.com nightly
+cargo +nightly run --release -p build-manifest build/dist build/manifest 1970-01-01 http://example.com nightly
 ```