On Sat, Dec 11, 2010 at 9:56 AM, Ozan Çağlayan <ozan@pardus.org.tr> wrote:
On 10.12.2010 23:49, Tiago Marques wrote:
I would also like to help with testing. I use Pardus 2007.x, if I recall correctly, and it was quite nice. Unfortunately the subsequent version was not very stable and I kind looked elsewhere. But it was mostly an easy to use distro, which was nice.

I'm still kind of new to trinity but tell me, how's bluetooth support? Broken right? Fixed in Pardus?


The problem with the kdebluetooth in KDE 3.5 is that it only works with BlueZ 3.x. It should not be too difficult to port it to the new BlueZ stack as it uses D-Bus calls instead of linking to bluez shared library.

We unfortunately currently ship blueman as our Bluetooth manager as we don't have enough power to make kdebluetooth work. blueman works out-of-the-box.


I see, thanks for the feedback. It's still a goal to have it ported then :)
How about network? Pardus config utilities or knetworkmanager?

Best regards
 
Timothy, the main development resides in kde/branches/trinity right? I'm gonna prepare a report for every base package consisting of what the patch I'm suggesting is doing, etc.

And also do you plan to split kde-i18n tarballs?

Thanks,
Ozan Caglayan