On 07/12/10 01:33 PM, jean.mccormack wrote:
It would look something like this:
<software_spec>
<destination>
<image ips_search_index="true">
</destination>
<software>
...
</software>
<software_spec>
The idea is that the generation of the ips search index is an
attribute on the IPS image we are creating as part of the DC process.
I believe that should work. Thanks
Sorry, after really looking at this I need the ips/cpio arguments to
fall under software, reason being that these
arguments can and often will change within a checkpoint but different
transfers within. Best served by an example....
In a checkpoint I really want to transfer via cpio files from:
/usr/bin with default cpio args
/usr/lib with cpio args "-pdm"
/usr/whatever with default cpio args.
I would really hate to break these up into separate checkpoints and if
the arguments are under software that's not needed.
So how about:
<software_spec>
<software>
<args name1=value1
name2 = value2>
</software>
</software_spec>
Actually.. wouldn't these values be a set of args to the Checkpoint? The
checkpoint element has an args element which is parsed character data. I
would think that the arguments for something like this would be
specified here.
sarah
Jean
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
