On Wed, Sep 24, 2008 at 8:55 AM, James Carlson <[EMAIL PROTECTED]> wrote: > Jason King writes: >> The problem is, as far as I can tell, with Indiana (aka OpenSolaris) >> there's no real concept of a 'full' install. You get a base set of >> packages, and then install whatever else you want as needed. This >> base set does not contain everything needed to build ON. I'm not sure >> installing everything on pkg.opensolaris.org is something that will be >> reasonable in the future, as more and more packages are added. If the >> current direction is still for SXCE to go away (replaced by Indiana) >> at some point in the future, this is an issue. > > Ah, that's a different issue. > > As currently documented, you cannot build ON on the OpenSolaris > distribution due to missing (and non-redistributable) packages. > That's why ON _requires_ the use of SX:CE. > > Installing "all" of the stuff in the Indiana repository still won't > get you a working build system. The packages needed to do the build > simply DO NOT EXIST there. You must get them from SX:CE. (There are > blogs that explain the details, presuming you have both the > OpenSolaris distribution and a couple of the SX:CE distribution.) > > For what it's worth, this is an Indiana (OpenSolaris distribution) > issue, and I'd recommend taking it up with that project team. There's > nothing that ON can really do about it. I assume that the Indiana > team will eventually address making it possible to build ON in some > manner, as they obviously _MUST_ do this in order to have SX:CE > terminated. It's an _obvious_ problem. > > (Really. You couldn't have thought that we would get rid of SX:CE > _before_ it was possible to build everything on the OpenSolaris > distribution ... could you? I'm sure we do things at times that turn > out to be foolish, but I seriously doubt we're that stupid.)
There are bits required that aren't redistributable (thus needing the packages off an SXCE iso). I know there are plans to create a repository hosted by Sun for those bits, but even once that's there, I don't think the issue goes away. The current solution would be to install everything from both repositories. As pkg.opensolaris.org gains more and more packages beyond what you see in SXCE today, I really question if 'install everything' is going to be a reasonable answer. I'm also not sure that I agree that it's an Indiana issue -- to me it's a lack of specificity All of the required packages have been identified (for the source tree as of Saturday morning). That list is is a little surprising (for example, requiring a database -- postgres -- be installed). My original question (restated, perhaps a bit clearer) is going forward, is there any attention being paid about putbacks that bring in new build requirements? Indiana is just probably the best example of why this is needed. Just saying 'oh well yeah we added this code to ON and to build it, it requires bash, staroffice, mysql, scheme, tcl, and gnu/tls, but that's someone elses problem' just doesn't sit well with me. I'd rather there at least be some sort of heads up about such things, so that the interested parties (such as the indiana team) could then update things as appropriate. _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
