search for: some_sourc

...> script (** Create a Python script object. The optional parameter [?name] is a hint for the name of the script. + The optional parameter [?tmpdir] is the temporary directory to use + (instead of creating a new one). + The parameter is the Python code. Usually this is [Some_source.code] where [some_source.ml] is generated from the Python file by [v2v/embed.sh] (see also [v2v/Makefile.am]). *) -- 2.21.0

...> script (** Create a Python script object. The optional parameter [?name] is a hint for the name of the script. - The optional parameter [?tmpdir] is the temporary directory to use - (instead of creating a new one). - The parameter is the Python code. Usually this is [Some_source.code] where [some_source.ml] is generated from the Python file by [v2v/embed.sh] (see also [v2v/Makefile.am]). *) diff --git a/v2v/utils.ml b/v2v/utils.ml index ccbb9d68a..7136e4be3 100644 --- a/v2v/utils.ml +++ b/v2v/utils.ml @@ -24,6 +24,10 @@ open Std_utils open Tools_utils open Common_g...

...name] is a hint for the name of the script. - The parameter is the Python code. Usually this is + The named parameter is the Python interpreter to use. Usually + you would use {!Config.virt_v2v_python_interpreter}. + + The unnamed parameter is the Python code. Usually this is [Some_source.code] where [some_source.ml] is generated from the Python file by [v2v/embed.sh] (see also [v2v/Makefile.am]). *) @@ -54,10 +57,3 @@ val path : script -> string try using/storing it beyond the lifetime of the program. This is used only where {!run_command} is not suitable. *)...

v1 was here: https://www.redhat.com/archives/libguestfs/2020-April/msg00007.html There's a BZ for this now which I forgot to add to the commit message: https://bugzilla.redhat.com/show_bug.cgi?id=1814611 For v2: - Fix incorrect reference to $TMPDIR in existing manual. - Separate handling for small temporary files and large temporary files. Small temporary files go into $TMPDIR

I rethought this again, as I think that it's a dangerous assumption to bake qemu-img measure output into our API. This patch series runs qemu-img measure behind the scenes, but then parses the output and sums it to a single number which we print. Doing that required a bit of reworking, moving the Jansson [JSON parser] bindings from virt-builder into the common directory and a couple of other