> I think that's basically the wrong angle of attack. We need to have > ON builds on the OpenSolaris distribution supported first (they're not > now). Once that's done, we need some way to manage the group of > packages that are required to be installed in order to build -- > including not just a mechanism (that looks simple) but also changes to > the work that the ON project teams do and the ON C-team checklist for > integration (naming the dependencies and verifying them). > > I think asking for random projects to shout their package requirements > out into the dark is an insufficient solution to the problem.
Hmm, I thought we currently did the "shout their package requirements" approach. At least, I've seen discussions with the ON gatekeepers prior to integrations that introduce new external package requirements, and subsequent heads-up messages from teams advising gatelings that they need at least package X from Solaris Y build Z for nightly to work. -- meem _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
