* Dave Miner ([email protected]) 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 *love* this idea. Personally, I'd really like it if pkg (specifically package creators) would create packages that were fully self-contained. By that I mean the package content is fully assembled for whatever use the package is intended for. So, things like this where the package specifies what objects are part of the boot archive and further if packages installed themselves in a 'ready to go' type of mode such that we could get rid of things like ICT's (or at least cut down on the amount) and have packages already configured ready-to-run with sane defaults upon installation of said package (though that's probably a much larger problem/goal). Anyway, my .02. Glenn _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
