From kde-bindings Tue Nov 21 09:35:54 2006 From: Sebastian Sauer Date: Tue, 21 Nov 2006 09:35:54 +0000 To: kde-bindings Subject: Re: [Kde-bindings] kdebindings in KDE trunk: how to move forward Message-Id: <200611211035.54253.mail () dipe ! org> X-MARC-Message: https://marc.info/?l=kde-bindings&m=116410174116589 Caleb Tennis wrote: > Any thoughts? While we are on that issue. I would like to start to prepare the move from Kross (currentlsy located in koffice/libs/kross/*). While things like core/* or modules/* would go to kdelibs, we still have the both Python and Ruby backends which wan't go to kdelibs. The question is, if it makes sense to have them in kdebindings too? maybe even integrate them into the hierachy somehow? Both bindings do depend on Qt4 + kross-core + the (python|ruby) interpreter but don't introduce new dependencies. Any suggestion? Thanks in advance :) -- Sebastian Sauer aka dipesh[sebsauer] http://www.dipe.org/public_key.asc Fingerprint: 8F1E 219B 16E6 4EC7 29CC F408 E193 65E2 9134 2221 Coder in http://www.koffice.org && http://www.kmldonkey.org _______________________________________________ Kde-bindings mailing list Kde-bindings@kde.org https://mail.kde.org/mailman/listinfo/kde-bindings