Jason King writes: > I actually filed the bug the other day -- but it still leaves the rest > of the world with basically on their own to discover any new > dependencies. I was just suggesting perhaps someone could at least > say 'btw, I just integrated X and it requires /bin/foo' when > integrating things that introduce _new_ rdependencies beyond what is > needed today
That's a consolidation issue. They're the ones who impose rules on projects that integrate. If you feel that this is the right thing to do -- despite the fact that the consolidation folks have been quite clear about the OpenSolaris distribution _not_ being supported yet for builds -- then you need to talk with the C-team. Since you seem to be primarily (only?) focused on ON, I suggest starting here: http://www.opensolaris.org/os/community/on/ [EMAIL PROTECTED] I think it'd be more fruitful, though, to get the OpenSolaris distribution officially supported for builds. Then you wouldn't need to worry about this. > versus leaving someone to spend 18 hours trying to figure > them out on their own (or worse, getting fed up and giving up and > going back to FreeBSD or Linux or really any other open source OS that > doesn't have this problem). How's that? SXCE works fine for those who want to build images, and is freely available. If you're trying to do it on the unsupported-for-ON-builds OpenSolaris distribution, then you're just plain on your own. That's what it means to be "unsupported" for that use. > But even if the whole world was only SXCE, why should ON require a > both a database and a webserver to compile? That's just ridiculous > IMO. What next? Where is the line drawn (if at all)? Currently, the line is bright and clear: if you need anything outside of what SXCE delivers, then you need to make special arrangements for it (such as modifying the ON build requirements). I guess I don't see why the requirements are "ridiculous." They might be annoying, and might not be well-factored, but frankly nobody has cared to factor out before them because (as previously described) the cost and risk are high (and continuous for new projects) and the return is non-existent. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
