search for: extra_args

...t all these occurrences, or did you just manually scan through the code? > diff --git a/sysprep/sysprep_operation.ml b/sysprep/sysprep_operation.ml > index 5c5640c67..1be5941c1 100644 > --- a/sysprep/sysprep_operation.ml > +++ b/sysprep/sysprep_operation.ml > @@ -172,7 +172,7 @@ let extra_args () = > assert !baked; > > List.flatten ( > - List.map (fun { extra_args = extra_args } -> > + List.map (fun { extra_args } -> > List.map (fun { extra_argspec = argspec } -> argspec) extra_args The last line here can be also simplified too? -- Pino...

..., target_data) { ans <- array(target_data) dimnames(ans) <- list(as.character(target_names)) names(dimnames(ans)) <- "x" class(ans) <- "table" ans } .check_identical <- function(target, current, varname, extra_args) { if (identical(target, current)) return() if (extra_args != "") extra_args <- paste0(", ", extra_args) cat("unexpected result for '", FUN_NAME, "(x=", varname, extra_args, ")...

Fix and/or document issues raised in this thread: https://www.redhat.com/archives/libguestfs/2017-February/msg00010.html Rich.

...environment, like an > R-level promise (but "promise" of course refers specifically to just > _lazy_ evaluation). > > For the uqs() thing, expanding calls like that is somewhat orthogonal > to NSE. It would be nice in general to be able to write something like > mean(x, extra_args...) without resorting to do.call(mean, c(list(x), > extra_args)). If we had that then uqs() would just be the combination > of unquote and expansion, i.e., mean(x, @extra_args...). The "..." > postfix would not work since it's still a valid symbol name, but we > could come...

...nd on the $PATH. We use this program to communicate with OpenStack so it must be installed to use this output mode.") + openstack_binary + in + (* We use this convenient wrapper around [Tools_utils.run_command] * for two reasons: (1) Because we want to run openstack with * extra_args. (2) OpenStack commands are noisy so we want to * direct stdout to /dev/null unless we're in verbose mode. *) let run_openstack_command args = - let cmd = [ "openstack" ] @ extra_args @ args in + let cmd = [ openstack_binary ] @ extra_args @ args in let stdout_f...

> version _ platform i686-pc-linux-gnu arch i686 os linux-gnu system i686, linux-gnu status major 1 minor 7.1 year 2003 month 06 day 16 language R Bug: integrate(f,lower,upper,extra_args) where f <- function(x,extra_args) { body } integrate doesn't pass the extra arguments when calling f. As a first check of this finding I integrated dnorm from minus infinity = to 1, with mu =3D -1 and sd =3D 7. As shown below the result is not = equal to pnorm(1,-1,7), but it is equal to...

...t;> R-level promise (but "promise" of course refers specifically to just >> _lazy_ evaluation). >> >> For the uqs() thing, expanding calls like that is somewhat orthogonal >> to NSE. It would be nice in general to be able to write something like >> mean(x, extra_args...) without resorting to do.call(mean, c(list(x), >> extra_args)). If we had that then uqs() would just be the combination >> of unquote and expansion, i.e., mean(x, @extra_args...). The "..." >> postfix would not work since it's still a valid symbol name, but we &gt...

Hi, this series improves virt-dib, adding some upstream changes, and refactoring the handling of output formats. Thanks, Pino Toscano (6): dib: clear up "already provided" message dib: add --checksum dib: pass custom mkfs options after the filesystem type dib: refactor output formats handling dib: clarify "output:" lines in --machine-readable documentation dib:

...nd the language object to the environment, like an R-level promise (but "promise" of course refers specifically to just _lazy_ evaluation). For the uqs() thing, expanding calls like that is somewhat orthogonal to NSE. It would be nice in general to be able to write something like mean(x, extra_args...) without resorting to do.call(mean, c(list(x), extra_args)). If we had that then uqs() would just be the combination of unquote and expansion, i.e., mean(x, @extra_args...). The "..." postfix would not work since it's still a valid symbol name, but we could come up with something....

Would this return a quosure? (i.e. a single sided formula that captures both expression and environment). That's the data structure we've adopted in tidyeval as it already has some built in support. Hadley On Friday, March 17, 2017, Michael Lawrence <lawrence.michael at gene.com> wrote: > Interesting idea. Lazy and non-standard evaluation is going to happen; the > language

...(string_of_location root_location) (string_of_inspection_data inspection_data) and string_of_inspection_data data = diff --git a/dib/output_format.ml b/dib/output_format.ml index 537469ab6..79a90ae35 100644 --- a/dib/output_format.ml +++ b/dib/output_format.ml @@ -106,7 +106,7 @@ let extra_args () = assert !baked; List.flatten ( - List.map (fun { extra_args = extra_args } -> + List.map (fun { extra_args } -> List.map (fun { extra_argspec = argspec } -> argspec) extra_args ) !all_formats ) diff --git a/generator/GObject.ml b/generator/GObject.ml index...

...m for portably checking rsync\n"); +} int main(int argc, char *argv[]) { - if (argc < 2) { - fprintf (stderr, "usage: " PROGRAM " DIR ...\n" - "Trivial file listing program for portably checking rsync\n"); + poptContext pc; + const char **extra_args; + char err_buf[100]; + int opt; + + pc = poptGetContext(PROGRAM, argc, (const char **)argv, + long_options, 0); + while ((opt = poptGetNextOpt(pc)) != -1) { + switch (opt) { + case 'h': +...

Per my previous email: https://www.redhat.com/archives/libguestfs/2017-September/msg00203.html I'd like to talk about requiring a more modern version of the OCaml compiler. These commits show some of the code changes which would be possible with OCaml >= 3.12 [which it turns out we already require by accident] and also with OCaml >= 4.02. The latter is my favoured option. Rich.

Fixes https://bugzilla.redhat.com/1256222

...;sysprep_operation.ml", line 1, characters 0-1: Error: The implementation sysprep_operation.ml does not match the interface sysprep_operation.cmi: Type declarations do not match: type operation = { name : string; pod_description : string; extra_args : ((Arg.key * Arg.spec * Arg.doc) * string) list; perform : Guestfs.guestfs -> string -> bool -> flag list; } is not included in type operation = { name : string; pod_description : string; extra_args : ((Arg.key * Arg.spe...

...Uwe Ligges _ > platform i686-pc-linux-gnu > arch i686 > os linux-gnu > system i686, linux-gnu > status > major 1 > minor 7.1 > year 2003 > month 06 > day 16 > language R > > Bug: > > integrate(f,lower,upper,extra_args) > > where > > f <- function(x,extra_args) > { > body > } > > integrate doesn't pass the extra arguments when calling f. > As a first check of this finding I integrated dnorm from minus infinity = > to 1, with mu =3D -1 and sd =3D 7. As shown below the res...

...to specify a path to remove."); +Use the I<--delete> option to specify a path to remove. + +You can use shell glob characters in the specified path; note that such +metacharacters might require proper escape. For example: + + virt-sysprep --delete '/var/log/*.log'."); extra_args = [ { extra_argspec = ("--delete", Arg.String add_paths, s_"path" ^ " " ^ s_"File or directory to be removed on guest"); extra_pod_argval = Some "PATHNAME"; -- 1.8.3.1

...rep_operation_hostname.ml index 51f9386..6f52e48 100644 --- a/sysprep/sysprep_operation_hostname.ml +++ b/sysprep/sysprep_operation_hostname.ml @@ -59,7 +59,7 @@ parameter. If the I<--hostname> parameter is not given, then the hostname is changed to C<localhost.localdomain>."; extra_args = [ - ("--hostname", Arg.Set_string hostname, "hostname New hostname"), + ("--hostname", Arg.Set_string hostname, "hostname\tNew hostname"), "\ Change the hostname. If not given, defaults to C<localhost.localdomain>." ]; diff -...

A mixed bag, but all the patches make sense together! Patch 1: Fix a bug that Tingting found: https://bugzilla.redhat.com/show_bug.cgi?id=1256222 Patch 2: Revert a patch that makes no sense now that we've added virt-v2v into base RHEL. This is just included because it's a cleanup needed before applying patch 3. Patch 3: Add the ability to use SSH identities (private keys) for virt-p2v

In the kernel and qemu communities it is routine for patches that will be backported to stable branches to be posted for review. I'm proposing we do the same for libguestfs stable branches. All of the attached have been tested with 'make check-release'. Rich.