Matt,
I would definitely say #2 is the correct approach.
As you probably know, in the old AI client, if no packages
to install were listed in the manifest, there was a hard-coded
list to fall back on (entire, babel_install, etc).
Is this list not specific to AI? If so, I would assume it should
be recorded within the AI code?
- Dermot
On 05/04/11 11:38, Matt Keenan wrote:
Hi
Came across a DTD issue, and would like some input.
In an AI manifest <software_data> element is optional and whether it contains a
list of packages is also optional, in AI what should happen in this context.
Currently in cud_ai, this results in no actual IPS packages getting installed
at all.
What is the corrective action here :
1 - Make software_data a requirement of software ? and also make it a
requirement to contain a list of packages/consolidations to
install/uninstall ?
or
2 - If software_data is empty or not provided at all within a software
element then by default install what's specified in default.xml :
<name>pkg:/entire</name>
<name>pkg:/babel_install</name>
What would happen if action is "uninstall", not an issue I suppose
as it will simply uninstall nothing, and should not cause a failure.
The list of default packages to install really should be stored in a central
location, rather than being hard coded into auto_install.py, any ideas where ?
cheers
Matt
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss