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.
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?
I'm not sure what you are referring to here. A single tarball containing
.po files currently exists for each supported language; are you referring
to splitting each tarball up further?
Thanks!
Tim