On 02/17/10 01:17 PM, Dave Miner wrote: > On 02/17/10 02:13 PM, Shawn Walker wrote: >> On 02/17/10 01:08 PM, Dave Miner wrote: >>> On 02/17/10 02:01 PM, Shawn Walker wrote: >>>> On 02/12/10 04:11 PM, Dave Miner wrote: >>>>> As you may recall, we reviewed a first draft of this design in >>>>> December/early January. I've finally published a revision which >>>>> addresses the comments I received, primarily from Jan and Ethan. >>>>> >>>>> While not exactly frozen, implementation work is underway based on >>>>> this >>>>> design so any remaining issues should be raised soon to allow the best >>>>> chance to address them. >>>>> >>>>> http://hub.opensolaris.org/bin/view/Project+caiman/AI+Image+Management >>>> >>>> "We propose to publish the AI boot image content into the pkg(5) >>>> repository as the package image/autoinstall...The Distribution >>>> Constructor will be extended to provide automatic publication of the >>>> images to a pkg repository if specified in the construction manifest." >>>> >>>> By publication of images, I'm assuming you mean a special package that >>>> essentially contains the list of packages that were in the original AI >>>> or Distribution Constructor manifest? >>>> >>> >>> It's a package that contains the actual, processed boot image. >> >> Will that package contain files that are already in other packages in >> the same repository? >> > > Yes, to some extent, but primarily not. You can take a look at an > existing AI ISO image to see what it would essentially contain, as it's > basically just a pkgsend of that structure. > >> If you intend to install the image using that package, it is also >> intended that packages be installed on top of that image? >> > > No.
Will it be clear to users that they shouldn't be attempting to create an image that contains a fully installed, pre-configured system and then attempt to perform package management of that resulting image? Will it be clear that isn't supported? Cheers, -- Shawn Walker
