Joseph Kowalski writes: > In any case, I don't see that keeping multiple versions of this stack on > Solaris makes any sense. We could build versions into the paths, doing > the moral equivalent of static linking (as seems to be proposed), but it > seems this would be counter to the assertions just made about path > compatibility being important when importing from the FOSS world.
If we have other system bits being delivered (such as subversion) that depend on out-of-date versions of the stack components, then what choice do we have? We either allow those other system bits to fail in the field, we deliver and manage to maintain multiple (accumulating) versions, or we somehow rewrite those other bits to deal with the stack's volatility. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
