On Thu, Jan 15, 2009 at 11:47 AM, Chris Quenelle <Chris.Quenelle at sun.com> wrote: > multiple compilers in /usr
This thread suggested at least two, and I can see more: the bundled one and the express one; we also have the version that can be used to compile OpenSolaris -vs- the one shipped by the compiler team, ... > very interesting challenge to deliver a subset of that product > into Nevada on a regular basis. ... which is why I suggested coming up with an overarching architecture... It doesn't have to be an "interesting challenge". It *could* be as simple as choosing which packages to co-bundle and install. The whole bundled/unbundled, /usr -vs- /opt thing is not set in stone. You could come up with another, better scheme. The problem I see in this case is that it is built on a lot of history, it assumes that some things can and other things can't be changed, and it has some vision for a future that changes based on who is doing the talking. My suggestion is to take a step back and ask what the best possible result might look like. When /I/ do that, I get something that smells a lot more like the Java JDK mechanism (everything under /usr/jdk/$version, with /usr/java being a symlink to the default version) than this current "some stuff in /usr, but other stuff that is the same, but different in /opt, depending on what time of day it is in Sun's compiler marketing department" :-) Of course, /your/ mileage may vary, may contain nuts, etc... -John
