On Fri, Sep 11, 2009 at 1:36 AM, Alan Coopersmith <Alan.Coopersmith at sun.com> wrote: > That would be a multi-day build, and adding X would still leave massive > amounts outside (SFW, GNOME, Mozilla, etc.).
Of course ) Leave it running over the holidays and use a more distributed/parallel make, than dmake. >> I still do not understand all aspects of how Sun does this internally. >> >> Every consolidation generates packages individually and just delivers >> them into a spool area? > > Yes. It just thought for a moment, maybe all gates should migrate to exactly the same build system. And every consolidation could be a pluggable module or that single build workspace, all using the same auto-configuration commands and make, the same spec files and so on. But maybe this would not be worth the effort, to forcefully equalize everything. Huge costs, not much benefit. >> Is there no automated A-to-Z tool, that compiles everything at once >> and then automatically combines the binary packages into a distro via >> distro-constructor (or in the past: How was it done for SXCE?). > > No. ? SXCE is built by combining the packages each consolidation delivers > to the common WOS "dock". ? ?OpenSolaris is currently built by converting > the SVR4 packages in that dock to IPS packages, with some transformations > along the way (the distro-import section of the IPS gate) - after the > SXCE builds stop, consolidations will start converting to delivering IPS > packages to a common repository. Ok, it is probably the most flexible and efficient way of doing things. Good, thanks for your explanation. -- %martin bochnig
