[Gtk-sharp-list] gphoto2 bindings

[Martin Baulig]

Rodrigo Moya <rodrigo@ximian.com> writes:

> all are conditionally built, so I think that shouldn't be a problem. For
> packages, just creating separated packages for each extra assembly with
> the extra dependencies should be enough.

Yeah, but you still get a source package which depends on them all.

> Of course, I still agree in not having not-general-purpose libs in GTK#.
> 
> > This also applies to people who're making binary packages: sure we can create a separate
> > binary package for each of these additional libraries, but we're ending up getting a
> > really large source package wich must obviously depend on all of them.
> > 
> > I was already a bit worried as gnome-db was included in gtk#, but didn't say anything
> > because I thought that this'd be the last and only one.
> >
> heh, gnome-db hasn't been the latest one, there have been a few others
> added after gnome-db, such as GConf, GStreamer, AFAIR.
> 
> I think, apart from gphoto, which clearly is a special case, the current
> libs in GTK# make a lot of sense, since they offer a complete framework
> for GNOME# apps. Maybe, it should be reanamed to GNOME# ? :-)

Well, I think it'd make sense to have all these GNOME libs in a separate package GNOME#
where gtk# is just gtk+ and the generator.  This may also help people on windows since
gtk# alone works on windows but all these GNOME libs do not, so people who want to have
their applications work on both platforms would use gtk#, but not GNOME#.

-- 
Martin Baulig
martin@gnome.org
martin@ximian.com