Hi, On Fri, 2006-04-14 at 08:30 -0700, Richard L. Hamilton wrote: > * the libs that _are_ part of supported [Open]Solaris need to be stable more > than they > need to be the latest and greatest. In particular, they need to satisfy > the requirements > of other Sun supported software (whether software that Sun controls or > leads the > development of, or whether software that Sun supports but isn't the lead > on) at the > versions corresponding to any given Solaris release. That is, while stuff > like JDS > should ideally not fall incredibly behind, it probably shouldn't be on the > bleeding edge
I'd completely agree with you on this one. The one thing that keeps me awake all night is how best to manage this. Given that most of the JDS stack is on a 6 monthly release cycle, it's pretty hard to not fall incredibly behind with the current Solaris roadmap. It would be nice to get the best of both worlds - perhaps the solution to that is encouraging binary compatibility, it's just an uphill battle. > I think in this regard, Blastwave may be on the right track, for the most > part. They > worry mostly about their own consistency, and depend on relatively few Solaris > libs, generally stuff that doesn't duplicate non-OpenSolaris OSS libs; that > decouples their update cycle from that of Solaris. Is that the right track, or ignoring the underlying problem? I'm not sure either way, but it feels like that involves a lot of needless duplication of work, and a significant amount of software swamps. Glynn
