Stephen Hahn wrote:
> Well, this seems like an entree to make my economic point. We cannot
> staff each OSS integration effort such that it could modify a
> significant subset of commands (or the system) to meet policies and/or
> advised changes on initial integration; the freeware team is at best
> able to choose to ship or omit components. (This choice means that,
> in some cases, dependencies will not be satisfied that might have been
> satisfied on other systems.) If an incoming set of bug
> reports/customer calls implies that additional investment is
> justified, then that team will have to come back to declare their new
> proposed interfaces.
Past experience with Sun project teams overwhelmingly shows that code
changes deferred at initial integration are almost never completed
later. We could choose to apply a different standard to OSS components,
but we shouldn't assume that they will become more compliant with
Solaris policies over time.
Scott
