Re: Time to heat up the new module discussion

["Elijah Newren" <newren gmail com>]

On 7/17/06, Jason D. Clinton <me jasonclinton com> wrote:
> On Mon, 2006-07-17 at 16:32 +0200, Murray Cumming wrote:
> > I don't have concerns about this that need addressing. Gtk# has simply not
> > been proposed for the Developer Platform during GNOME 2.15/2.16.
>
> So, I am seeking clarification, not trying to start something ... Are
> you saying that Tomboy cannot be considered for inclusion in 2.16
> because the necessary step of proposing GTK# for official GNOME platform
> bindings inclusion has not taken place?
>
> Again, I am not trying to put words in your mouth. I just want to
> understand what's being said ...

He was just trying to correct your email.  Your original email said that
 "I spent two hours reading every email sent in April, May and July
about including
  Mono as an official part of the GNOME platform"
which was misleading.  We have a "platform" release (with certain
API/ABI rules), a "bindings" release suite (with different API/ABI
rules), and a "desktop" release.  Mono has not been proposed for the
"platform" release; it was proposed for the "bindings" release.
Murray was just trying to clarify that.

If you're still wondering about the dependency issues, it's basically
this: Modules in the platform cannot depend on modules in the other
two releases (that would violate the API/ABI constraints).  Modules in
the bindings release cannot depend on modules in the desktop (that
would violate the API/ABI rules as well).  desktop modules can depend
on the platform modules, and, currently, can depend on the python
bindings but not the others.  The huge threads and arguments are about
whether desktop modules should be allowed to depend on other bindings
that are in or are proposed to be in the bindings release (in
particular, Gtk#).