Sarah,
Partial review covering just Software and Execution schema. More later.
One structural suggestion on the doc: you might combine the text in 5.3
with the actual proposed schemata from 6.1 on. The element/attribute
tables in 5.3 didn't really add anything from my point of view. This
would also eliminate potential inconsistencies between the two (I didn't
note any yet, fortunately).
6.1 Software spec
- What is an "unknown" action?
- What's the purpose of the "unknown" type?
- What purpose does the "compression" attribute serve?
- I'm not quite sure how I'd map the primary_source and secondary_source
attributes to the multiple publisher, multiple origin and multiple
mirror configurations that are possible (indeed, likely) in pkg. Maybe
we just need more examples.
- The example in B.3 shows a "noinstall" action, but that's not legal
according to this schema.
- How would we handle pkg publishers such as extra or support that
require key/cert specification?
6.2 Execution
- I'm not sure why we should have software_spec embeddable within a
checkpoint, but target data (for example) not?
- I'm unclear on the semantics of the mod_name attribute.
- What is the type attribute of log_handler used for? I couldn't map it
to the Logging v1.5 spec functions.
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
