Re: Currnet CVS fails to configure - the patch

[Marius Vollmer <mvo@zagadka.ping.de>]

Ariel Rios <ariel@arcavia.com> writes:

> > If we need all this complexity for Gtk 2.0, we should make a
> > branch for this in guile-gtk.
>
> We depende on a new Gtk 1.2 release but I am starting to wonder if
> Owen / Havoc will ever do one.

Ok, we need to make some progress on this.

There are two issues: generating the build scripts from their sources
(i.e. configure.in -> configure), and running the build scripts from a
tar ball (i.e. running configure).  Let's call the people who do the
first thing `developers', and the rest `users'.

The ideal thing would be to have a single guile-gtk package for all
versions of Gtk+.  We should try hard to achieve this.  (That is, no
branch.)

It is OK when developers need to get extra stuff like gnome-common and
pkg-config even if they are not using Gtk+2.  It is not OK that users
need these packages if they are not using Gtk+2.

Right now, it is more important that guile-gtk works for the 1.2.x
branch of Gtk+ than that it works for the upcoming 2.0.  So the first
thing we need to do is to make sure that the generated configure
script runs on a system that does not have gnome-common or pkg-config
or glib.pc, etc.

Essentially, configure should be reverted to its old behaviour when
pkg-config is not found, and just use gtk-config.


Is this OK with everyone?