@@ -73,8 +73,7 @@ automatically.</para>
7373 <listitem ><para >Optionally, a single <emphasis >manifest</emphasis >
7474 file is created that contains the same metadata as the
7575 <filename >.narinfo</filename > files. This is for compatibility with
76- Nix versions prior to 1.2 (see <command >nix-pull</command > for
77- details).</para ></listitem >
76+ Nix versions prior to 1.2.</para ></listitem >
7877
7978 <listitem ><para >A file named <option >nix-cache-info</option > is
8079 placed in the destination directory. The existence of this file
@@ -135,7 +134,7 @@ automatically.</para>
135134 <varlistentry ><term ><option >--manifest</option ></term >
136135
137136 <listitem ><para >Force the generation of a manifest suitable for
138- use by < command >nix-pull</ command > . The manifest is stored as
137+ use by old versions of Nix . The manifest is stored as
139138 <filename ><replaceable >dest-dir</replaceable >/MANIFEST</filename >.</para ></listitem >
140139
141140 </varlistentry >
@@ -203,20 +202,6 @@ $ nix-push --dest /tmp/cache $(nix-instantiate -A thunderbird)
203202
204203</para >
205204
206- <para >To generate a manifest suitable for <command >nix-pull</command >:
207-
208- <screen >
209- $ nix-push --dest /tmp/cache $(nix-build -A thunderbird) --manifest
210- </screen >
211-
212- On another machine you can then do:
213-
214- <screen >
215- $ nix-pull http://example.org/cache
216- </screen >
217-
218- to cause the binaries to be used by subsequent Nix operations.</para >
219-
220205<para >To generate a signed binary cache, you must first generate a key
221206pair, in this example called <literal >cache.example.org-1</literal >,
222207storing the secret key in <filename >./sk</filename > and the public key
0 commit comments