On Thu, 9 Sep 2010, Dave Miner wrote:
On 09/ 8/10 06:24 PM, Alok Aggarwal wrote:
The DC manifests for the various x86 media types currently
have a section for boot_archive_contents that defines
what gets included in the x86 boot_archive.
Each of these manifests (slim_cd_x86.xml, all_lang_slim_cd_x86.xml,
text_mode_x86.xml and ai_x86_image.xml) has a such a section.
The contents of this section are more or less the same across
these manifests[1].
As we're re-writing DC[2], it make sense to re-evaluate whether
the boot_archive_contents can be factored out into a common file
that can then be referenced in each of the various manifests.
Another avenue to explore is to not have this list at all in the manifest;
instead, tag those objects in the packages as they're published by the
consolidations with some appropriate attribute. Then DC's checkpoint that
constructs the boot archive could just use pkg search to compile the list of
files and directories to transfer.
I kicked around this idea as well. Couple of things
as I thought about it some more:
. Wouldn't this make it harder for consumers that want
to customize the contents of their boot_archive harder?
Granted, it's the minority case but it's still a set
of consumers we've got to think about.
. Tagging the boot_archive files in pkg doesn't infact
take away the burden of having to maintain and evolve
them as changes in other parts of the ecosystem take
place. It merely seems to shift the burden from DC over
to pkg(5) - would that be an accurate assessment?
Alok
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
