Hi, firstly, thanks to everyone having contributed to the discussion so far, reading it has been very interesting and helpful to understand better the structures OpenSolaris development teams act in.
I totally agree that the top priority should be making Indiana a supported build platform, but haven't you touched a fundamental issue here? IMHO, if a consolidation is not self-contained, any change in the build environment which is not reflected in the runtime environment can have adverse effects, just think of library version dependencies. Considering the immense effort Sun developers spend on maintaining Solaris distributions, I thought some well maintained documentation about interdependencies between the various consolidations would already exist. I don't understand how, for example, s10 patch requirements could be generated without such documentation. I was assuming that the dependencies in the pkgdefs were used for this process, but how, even within ON, are dependencies on specific versions documented to get patch dependencies right for the final build? And how is the problem of inter-consolidation dependencies solved for Solaris? Apparently, there is a lot I don't understand yet. I would highly appreciate if someone from Sun could explain these processes or point to documentation which I have missed. Thank you, Nils _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
