> Well, if the interfaces are stable, then maybe the _headers_ can be > placed into ON to facilitate this kind of building.
Ick. If the interfaces are stable, the build system's headers should suffice. Pulling everything into ON is not a tractable approach. (Why stop there? Why not put the compiler itself into ON? How about gcc? This just isn't the way forward.) > Basically, I believe ON is a _foundation_ for the technology, right > after the compilers themselves, and it should be possible therefore to > bootstrap without a lot of external dependencies. I don't see the distinction you're making between the compiler and the libraries. Both are part of a well-defined build environment that's needed to build ON. Both are satisifed by installing packages. > Alternatively, if the interfaces are stable, what is the value of having > the library _outside_ of ON? Because it becomes a hairball -- you'd end up dumping in the closure of dependencies needed by each *implementation* of each interface (command, library, or whatver. As an example, it's not reasonable to say that ON's source files cannot use Java because the Java source is not in ON. -- meem _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
