Displaying 3 results from an estimated 3 matches for "disable_foo".
2014 Jan 07
2
Re: [Bug 1046905] New: RFE: add argument to virt-sysprep to disable individual default operations
On Friday 27 December 2013 10:58:15 you wrote:
> virt-sysprep either runs with all default operations or a selected
> list of operations with the --enable argument. A few times I've
> found I'd like to use the default list, but minus one or two
> operations in particular, however there's no easy way to specify
> this.
>
> A --disable argument that took the
2014 Jan 07
0
Re: [Bug 1046905] New: RFE: add argument to virt-sysprep to disable individual default operations
...allow multiple and concatenate them together? So that
--operations foo,bar --operations -baz
would be equivalent to
--operations foo,bar,-baz
?
Multiple --operations could be useful for scripting, ie. it would let
shell users write:
opts="--operations all -a disk.img"
if [ $disable_foo ]; then opts="$opts --operations -foo"; fi
Another thing to test is whether the OCaml argument parser[1] can
handle '--operations -foo' without thinking that -foo is a separate
arg.
Rich.
[1] It is not as sophisticated as GNU getopt, and a very long way from
Perl & Python...
2014 Jan 07
2
Re: [Bug 1046905] New: RFE: add argument to virt-sysprep to disable individual default operations
...operations foo,bar --operations -baz
>
> would be equivalent to
>
> --operations foo,bar,-baz
>
> ?
>
> Multiple --operations could be useful for scripting, ie. it would let
> shell users write:
>
> opts="--operations all -a disk.img"
> if [ $disable_foo ]; then opts="$opts --operations -foo"; fi
I agree, allowing multiple --operations is a good thing. After all,
given the proposed behaviour, every --operation would alter the existing
set of operations (empty at the first --operation invocation, as with
--enable), instead of starting f...