On 07/12/10 01:50 PM, Sarah Jelinek wrote:
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.
Are these args something the user should have control over? Are these
set in the application?
Possibly? But ips_search_index also falls into the category of I would
like it under software. All the IPS ones do.
In fact, you have 3 types of IPS argument lists, one for creation of the
image, one for pkg installing and one for
pkg uninstalling. So if a checkpoint does a image
create/install/uninstall that is 1 software_spec node but 3
software nodes. How do I know which one to apply the arguments listed in
image to? The idea behind these arguments
is that I'm not supposed to have to be aware of what arguments there
are, just pass them through to IPS.
And in reply to your email I just got:
"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."
No for the same reason as above. They really need to not be checkpoint
specific but rather which actual transfer you're doing specific, the key
being I may do n transfers/checkpoint.
Jean
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>
Jean
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
