What's the problem with them being in different consolidations?
We have lots of cross-consolidation dependencies, including those of
External/Volatile interfaces. The only obvious complication
I see is that if OpenGrok and CTags are in different consolidations, a
contract will be needed for the interfaces used, since Volatile interfaces
are treated as effectively Consolidation Private for Contract purposes.
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
Brian Utterback wrote:
> Another issue has come up. The OpenGrok case (pending, not yet
> submitted) has a dependency on Exuberant CTags. In fact, this dependency
> is what has delayed the filing. In any case, the desire is to have
> OpenGrok integrate in the SFW consolidation for inclusion in
> OpenSolaris. However, OpenGrok requires Exuberant CTags to run work.
> Since this case proposes to integrate Exuberant CTags into the DevPro
> consolidation, this leaves us with a quandary.
>
> One possibility is to deliver OpenGrok into DevPro. The OpenGrok team
> wants to deliver to OpenSolaris, I don't know how the DevPro people feel
> about this. Another is to deliver Exuberant CTags into SFW. I suspect
> that the DevPro people will still want it in DevPro because of the
> support of prior Solaris versions and other platforms. And the last
> possibility is to deliver a private copy of Exuberant CTags with
> OpenGrok, suitably disguised to prevent users from finding it.
>
> Is there a precedent for this situation? Any idea on the best course of
> action?
>
