More comments about software_spec....
Currently transfer supports the ability to modify the default cpio args
from -pdum to whatever. Most of the time it's -pdum but there are some
exceptions (liveCD has one of those) where you want something else.
Should a non-default cpio argument be shown in the manifest? Or are we
relying upon the application to know and write that into the DOC?
Is the name for software_spec really optional? If it doesn't have a
name, I really don't have a way of figuring out the checkpoint/DOC
relationship.
Now on to software spec and how it relates to the ips functionality.
Like Alok, I'm concerned about the primary and secondary source
definitions.
You only allow 0-1 primary source and 0-1 secondary source. I would say
0+ for secondary.
For me it would be nice to have the primary/secondary sources you
specify in the dc area to be in the software_spec area. If I can't get
them from parsing the manifest, then Alok will need to put them into the
DOC for me which just adds more work for him and more risk.
How about getting rid of the concept of primary and secondary and doing
something like this?
/<source type="primary"> # other types could be secondary,
post_primary, post_secondary/
/ <publisher name="opensolaris.org"> /
/ <origin name="http://ipkg.sfbay/dev";></origin> /
/ </publisher> /
/ <source> /
Alok had also asked about where the IPS arguments get specified. Is this
something we want in the manifest? Or is it something the application
will supply on it's own? There are several other attributes that IPS
transfer has that fall into this same category (is_zone flag,
image_type, and a purge history boolean) that have a default value that
will usually be used but in the non-default case where does this info
come from, manifest or app?
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
