Rudolf Kutina wrote: > Hi All, > > As part of creating some prototypes of Virtual Appliances on OpenSolaris > 200811 I am working on > reducing standards GUI based OpenSolaris into something smaller (Building > sort of OpenSolaris JeOS). > > Yes, In future we want to use officila ways as they evolve like "Distro > Constructor" and/or "Automated Installer" for OpenSolaris JeOS creation, > but for now we need to understand how select and prove set of packages for > OpenSolaris JeOS and get deeper sense of underlying principles. > > For this I need to better understand role of "virtual" packages entire and > slim-install in OS distro live cycle. > > 1. What is the purpose of entire package ? >
Because of the way we build OpenSolaris, we want packages from a build installed as a complete set by default. Right now we're reving package versions w/ every build; that will change. [EMAIL PROTECTED] gives us a way to say "this was the set of packages that comprise build 101" for example. > 2. What is different between in this virtual packages types: entire and > slim_install ? entire's dependency mechanism just specifies which version of a package, if installed, should be present. slim_install is just a regular group package. > > 3. Do I need to have entire in installed system or for to have pkg > > image-update funstional ? > > Yes, or the equiv. definition for your distro. 4. If entire like package is needed, how I can create it from my pkg list and how to publish it in my IPS repo ? Take a look at the Makefile in src/util/distro_import; all the logic and mechanism are there. - Bart -- Bart Smaalders Solaris Kernel Performance [EMAIL PROTECTED] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
