[Gtk-sharp-list] Versioning and Unstable Gtk#

Todd Berman tberman at off.net
Sun Jul 10 21:59:38 EDT 2005

On Sun, 2005-07-10 at 21:31 -0400, Ben Maurer wrote:
> Hey guys,
> I've been working with tseng, our fearless Ubuntu packager on packaging
> Gtk# 2 apps. It looks like we are pretty clearly not going to be api
> frozen soon enough to make it a good idea to ship Gtk# 2 in the GAC.
> So, I suggested that we include a pre-release gtk# in the private bin
> path for gtk# 2 apps (muine and monodevelop). However, when I was
> thinking about this, I realized we had a little problem.

This is the worst solution you could ever come up with to this problem.

I have an idea. How about ubuntu ships what is the latest release at
that time and we go from that. If people just stick to the stuff in
ubuntu's repo, then they are fine, and if people start using the latest
gtk#, then obviously they are going to need to use the most recent
version of its various consuming applications. Such is the suck of
riding along the newer development lines.

I dont really see any of this as a 'big' deal, Ubuntu will ship another
release in 6 months.

All 3 of your hackish solutions add *permanent* issues we will have to
deal with, where as just dealing with the suck, the issues go away in 6

I am not confident that we will see another MonoDevelop release until
the stable gtk# release regardless, so 0.7 is what would be current at
that time anyway.

Just as an aside, no MonoDevelop that ships a internal gtk# or a weirdly
versioned gtk# through any means will ever be supported. As in, don't
file your bugs with us, because that is not a sane way to deploy any
application, especially a development environment.


More information about the Gtk-sharp-list mailing list