[Kde-bindings] Fwd: Re: Pre-approved Languages

[Jonathan Riddell]

On Thu, May 01, 2008 at 04:53:54PM +0200, Sebastian Sauer wrote:
> why not do it like we did with e.g. the Ruby Plasma backend and move it to 
> kdebindings itself? The applet depends on python, that's what 
> kdebindings/python/* is for. The applet depends on PyKDE which is in 
> kdebindings/python/pykde4...
> 
> probably someone could argue that we would end with a kdebdings that depend on 
> every other module, specially one more wrappers/libs come in, but we could 
> still try to organize this somehow within kdebindings.
> 
> I mean, what happens if someone writes now an applet using QtRuby and moves it 
> to kdeutils too. Would kdeutils end to depend on ruby, python, C#, java, ...? 
> imho that's at least something that was solved in kdebindings with the (ruby| 
> python|csharp|java|...) subdirs. That way an distributor could just package 
> everything that depends on python and provide one big kde-(ruby| python|
> csharp|java|...) tarball and if that's not enough, we could still add a 
> theird hierachy to group things a bit.

kdebindings is a module for language bindings, not for applications
that happen to use those bindings.

kdeutils is a module for applications.  There's no paticular
restriction on what it can depend on, except of course circular
dependencies.

Jonathan