[Kde-bindings] kdebindings in KDE trunk: how to move forward

[Simon Edwards]

On Tuesday 21 November 2006 10:35, Sebastian Sauer wrote:
> Caleb Tennis wrote:
> > Any thoughts?
> While we are on that issue. I would like to start to prepare the move from 
> Kross (currentlsy located in koffice/libs/kross/*). While things like core/* 
> or modules/* would go to kdelibs, we still have the both Python and Ruby 
> backends which wan't go to kdelibs.
> The question is, if it makes sense to have them in kdebindings too? maybe
> even  
> integrate them into the hierachy somehow?
> Both bindings do depend on Qt4 + kross-core + the (python|ruby) interpreter 
> but don't introduce new dependencies.

Putting the Python backend for kross in kdebindings/python makes sense to me 
at least.

cheers, 

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