Comment 3 for bug 289402

Using the current information we came up with following options:
1) dump the patches
2) don't build ruby/smoke with plasma bindings (that is assuming there are no other workspace dependencies, which I am not sure about)
3) add the necessary patches to get all the kdebase-workspace deps moved from bindings to workspace (according to upstream changes in KDE trunk)
4) debundle the python stuff from kdebase-workspace into a sepearte source package
5) leave it alone

With the following disadvantages:
1) the seperate examples package would end up empty + user confusing because of disappearing features
2) disappearing features again
3) difficult to do + not very regression-save
4) the python bindings would need a new package and apt-get update doesn't install new packages automagically, so we would have to communicate the need for dist-upgrade, which is kind of difficult considering libplasma is one of the most essential parts of the KDE 4 desktop, not making libplasma depend on teh python bindings would again be disappearing features
5) no LPIA and HPPA builds (although mobile stuff is only getting upstream attention in 4.2 and we still didn't hear of any HPPA KDE users)