[Kde-scm-interest] kdebindings split

[Ian Monroe]

Just to be clear from the start, this is only for 4.7 and not 4.6.
Nothing has changed for 4.6; it will continue to be developed in SVN.

The main thinking behind this split is to make the dependency tree
clearer. Before there was a cmake-time dependency on KDE. This
resulted in some very real confusion among new kdebindings
contributors (and even a quasi-fork). This also frees us to release
kdebindings modules at different times (for instance Qt modules with
Qt releases, KDE modules with KDE releases). This hasn't been decided
precisely at this time.

Many distributions already split up kdebindings in a similar manner,
so I do not see this being an issue.

Copying and pasting from README.MODULARIZATION:
In anticipation of the conversion to Git, the trunk kdebindings module
has been modularized. This means you can no longer build it all at once as
before.

The 'root' of kdebindings builds only the Kross modules. In git all the kross
modules will be in one repository. Kross modules depend only on KDE and do not
require other kdebindings modules.

All other modules will be in separate repositories, as detailed below.

Dependency Tree:

generator (will be named smoke-base once we are in git)
 |- smoke/qt
    |- ruby/qtruby
    |- perl/qt
    |- csharp/qyoto
    |- smoke/kde
       |- ruby/korundum (also depends on ruby/qtruby)
       |- perl/kde (also depends on perl/qt)
       |- csharp/kimono (also depends on csharp/qyoto)
       |- python/pykde4