[Kde-scm-interest] Splitting kdebindings when moving to git

[Arno Rehn]

Hi again,

I know that splitting the monolithic KDE modules into different git-repos has 
been discussed a thousand times here and that you're probably pretty much fed 
up with it. However I have to bring it up again:

With KDE bindings we have the problem that many people only want the Qt-
specific part of the bindings (like QtRuby or Qyoto) - and then only for one 
language. Having all of the different bindings in a KDE module makes it 
difficult for them to install only the Qt portion and even prevents some 
people from contributing (there's already a fork of QtRuby on github, because 
people don't like checking out the complete kdebindings and then going through 
the hassle of figuring out how to compile only QtRuby).

Would it be possible to have some of the bindings in a seperate repository, 
either under a 'kdebindings' umbrella or - maybe even better - in kdesupport?

We could then also coordinate Qt-bindings releases with the Qt releases, which 
is obviously very important for bindings and doesn't work too well if the 
bindings are released every half a year with the rest of KDE.

Thanks in advance and sorry for bringing that topic up again,
-- 
Arno Rehn
arno at arnorehn.de