Non-C++ Apps in KDE Main Modules (Was: Guidance in KDE Admin)

Allen Winter winter at
Thu Mar 27 14:00:52 CET 2008

On Wednesday 26 March 2008 16:17:53 Leo Savernik wrote:
> Am Mittwoch, 26. März 2008 schrieb Nicolas Ternisien:
> > >  >  All modules need porting to KDE4 (and could make nice showcases for
> > > the Python >  bindings then). Mountconfig would also need porting to
> > > Solid (it already uses
> [...]
> > No other opinion ? If you agree, just say Yes/+1 or No/-1, just to be
> > sure this is something useful, and that will help KDE Admin being more
> > interesting.
> It looks like Guidance introduces a hard python dependency into KDE. I
> don't particularly like that. Is there any precedent that justifies a hard
> runtime python dependency?
I think the Release Team should discuss this and provide a policy statement.

Do we allow Python/Ruby/C#/Perl etc. apps in the KDE main modules?
If so, which ones and why?

Oh, and this is also needed for Jonathan's system-config-printer-applet

Here are some off-the-cuff thoughts to get the ball rolling:

For the language
1)  must have a  mature, working, kde binding (i.e. there isn't a
working perl binding IIRC)
2) must be mature and operational on all our target platforms
3) must be able to provide full translations and internationalizations

For the app:
1) must follow the kde look-and-feel, widgets, etc

More information about the release-team mailing list