Richard L. Hamilton wrote: > How about an additional criteria for what's eligible to be moved out: > no consolidation private interfaces used, nor any project private ones > unless the whole "project" is moved out? That way, there aren't a bunch > of new contracts needed, nor increased risks of out-of-sync changes.
That sounds like good guidance to me. This pruning was actually done previously and is the reason the SFW consolidation exists today. One of the things high on my list to get out of ON into SFW is OpenSSL - doing so isn't as trivial and obvious until you know all the quirks of where OpenSSL is used in ON though. I think it would be hard without creating a new consolidation to move things out of ON that don't also exist elsewhere. For example Sendmail, OpenSSL are good candidates but I think that the Solaris 'cat, csh' are poor candiates. Why because they have never been built anywhere but ON. If the goal here is based around how much stuff needs to be brought over to build then I'd highly recommend those that haven't yet play with the onnv-gate Mercurial repository. It is orders of magnitude faster for bringover/putback (pull/push) than Teamware and won't need deleted_files in the long run either. If the goal is less build time then I'm not sure how much impact there would be from moving out small utils/libs. If the goal is to build external to OpenSolaris FOSS with its own build tools then moving those things out of ON into somewhere like SFW is a great goal - and this is why I want OpenSSL out of ON. -- Darren J Moffat _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
