Re: [ruby-gnome2-devel-en] problem running cvs version

[Markus J. <mj...@we...>]

Hello
I am not an expert an gtk and glib but I think your choice was a good one.
seperating it into many packages migth turn out to be confusing

one suggestion when ruby-gnome2 is stable.
release two packages

- one complete package with all the gnome stuff
- one package only with gtk2 and glib2

many users do not want to use gnome because it is not portable to windows

so, when you make a package gtk2 and glib2 and the installation process
can install both it is easy for the users and nobody has to worry about 
gobject and all the stuff

so I think it is good the way you did it.

markus


On Sunday 15 September 2002 14:03, Masao Mutoh wrote:
> Hi,
>
> On Sun, 15 Sep 2002 13:31:32 +0200
>
> Markus Jais <mj...@we...> wrote:
> > just on more question for my understanding.
> > why is glib2 needed. I thought this has only some convenient types
> > and memory routines for C programmers.
> > why is this needed for ruby??
> > just curious!
>
> Hmm ...
>
> glib package(not ruby) includes glib, gmodule, gobject, gthread.
>
> I think we do not need to implement glib.
> Because almost of the functions will not use with Ruby.
>
> But we need gobject and some other functions in glib package.
> Especially GObject <-> Ruby conversion is very important part of
> Ruby-GNOME2.
>
> At first, I thought separated 'glib' and 'gobject',
> but it became to overdo, it was enough one library.
> So I decided this to use here as glib package name.
>
> And I think other utility functions which will be used whole of
> Ruby-GNOME2 define in Ruby/GLib.
> It makes easy to implement Ruby/GTK and other library which support
> GType system.
>
> But I read your comment, it may be better to separate 'glib',
> 'gobject', and utilty functions ...
>
> Any comments?

-- 
Markus Jais
http://www.mjais.de
in...@mj...
The road goes ever on and on - Bilbo Baggins