[Kde-bindings] Re: py(Qt|KDE) and KDE CVS

[Simon Edwards]

On Tue, 23 Mar 2004 03:00 am, Richard Dale wrote:
> On Monday 22 March 2004 16:23, Marcus wrote:
> > On Monday 22 March 2004 9:09 pm, Simon Edwards wrote:
> > > I'll try to explain the reasoning for wanting to have the python 
bindings
> > > distributed separately from a monolithic kde-bindings tar ball.
> >
> > The Qt# project distributes a copy of QtC from outside of kdebindings is
> > that the configure script for kdebindings seems to insist upon a working
> > KDE installation, and many people who wanted to try Qt#, which has QtC as 
a
> > dependency, were not KDE users and did not want to install KDE just to try
> > Qt#.

> I'd like to retire the QtC bindings. I haven't been able to generate them 
for 
> several KDE releases because the Qt# build depends on them. Because I 
haven't 
> been able to regenerate the C bindings, the Objective-C bindings project 
fell 
> apart before it was even released.

So in summary, which bindings *are* kept up to date and working? Which ones 
can be relied on from release to release?

-- 
Simon Edwards             | Guarddog Firewall
simon at simonzone.com       | http://www.simonzone.com/software/
Nijmegen, The Netherlands | "ZooTV? You made the right choice."