On Fri, Sep 28, 2001 at 10:03:31PM -0400, Jonathan Pennington wrote:
> Why does pygtk1.99 suddenly have so many dependancies that I can't find?
> Pkg-config? Pango? I have glib installed but it cannot source it? I've
> installed older versions fine, but have to fight with this one just to
> configure it. Is there something I'm missing?

It's hardly a sudden change. Pygtk-1.99 is based on the gtk-1.3 line of
products. The old gtk-config (and gnome-config and foo-config for your
favourite foo) have now been replaced by pkg-config and a simple file
for each package -- much easier after the initial learning hump.

Also, for better i18n handling, pango exists and gtk depends on it.
Also, there is atk (the accessibility toolkit) in the dependency chain,
too (gtk depends on it). 

I don't know what you mean by not being able to source glib -- are you
using glib-1.3.x and is pkg-config in your path (since that wil be
needed by things that want to link against gtk, atk, pango and glib)? If
you give more information here, we can probably help you.

> I've been working with 6.8 and Python2.2a3-4 just fine, but there's a
> problem I'm running into now that I think might be caused by the
> mis-match (or my sucky programming, one or the other), so I thought
> I'd give the new
> pygtk version a try. 

The latest snapshot of pygtk (1.99.2) requires the Python 2.2a4 release,
since it relies on one of the things that changed from alpha 3 to alpha
4. So if you are using the absolutely latest and greatest stuff, you
need to be using the latest Python alpha as well.

Hope this helps clarify the floor plan somewhat.

Cheers,
Malcolm

-- 
Support bacteria - they're the only culture some people have.
_______________________________________________
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk

Reply via email to