Blame SOURCES/0073-v2v-vddk-Further-rework-documentation.patch

151578
From 9e64238a389264b34af20b49da929d5bf6ccd436 Mon Sep 17 00:00:00 2001
151578
From: "Richard W.M. Jones" <rjones@redhat.com>
151578
Date: Tue, 7 Nov 2017 11:32:16 +0000
151578
Subject: [PATCH] v2v: vddk: Further rework documentation.
151578
151578
Thanks for suggestions from Ming Xie.
151578
151578
(cherry picked from commit 12d87361a4623587c53196e70157448158c02c7f)
151578
---
151578
 v2v/virt-v2v.pod | 18 ++++++++++++------
151578
 1 file changed, 12 insertions(+), 6 deletions(-)
151578
151578
diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod
151578
index 48a20cccc..417c25331 100644
151578
--- a/v2v/virt-v2v.pod
151578
+++ b/v2v/virt-v2v.pod
151578
@@ -1304,6 +1304,10 @@ library is permitted by the license.
151578
 
151578
 =item 2.
151578
 
151578
+VDDK E<ge> 6.5 is required.
151578
+
151578
+=item 3.
151578
+
151578
 You must also compile nbdkit, enabling the VDDK plugin.  At least
151578
 nbdkit E<ge> 1.1.16 is required, but it is usually best to compile
151578
 from the git tree.
151578
@@ -1320,12 +1324,14 @@ L<https://github.com/libguestfs/nbdkit/tree/master/plugins/vddk>
151578
 
151578
 =back
151578
 
151578
-=item 3.
151578
+Compile nbdkit as described in the sources (see link above).
151578
 
151578
-You do B<not> need to run C<make install>.  You can run nbdkit from
151578
-its source directory.  Set C<$PATH> to point to the nbdkit top build
151578
-directory (that is, the directory containing a shell script called
151578
-F<nbdkit>), eg:
151578
+You do B<not> need to run C<make install> because you can run nbdkit
151578
+from its source directory.  The source directory has a shell script
151578
+called F<nbdkit> which runs the locally built copy of nbdkit and its
151578
+plugins.  So set C<$PATH> to point to the nbdkit top build directory
151578
+(that is, the directory containing the shell script called F<nbdkit>),
151578
+eg:
151578
 
151578
  export PATH=/path/to/nbdkit-1.1.x:$PATH
151578
 
151578
@@ -1333,7 +1339,7 @@ F<nbdkit>), eg:
151578
 
151578
 You must find the SSL "thumbprint" of your VMware server.  How to do
151578
 this is explained in L<nbdkit-vddk-plugin(1)>, also available at the
151578
-link given in item 2 above.
151578
+link above.
151578
 
151578
 =item 5.
151578
 
151578
-- 
151578
2.14.3
151578