Hi,
Pardus is a Linux distribution funded and developed by the Turkish Government. We're planning to release a Corporate version - Pardus Corporate 2 - which is based on KDE 3.5.
We've been maintaining KDE 3.5 for a very long time so we have a lot of bugfix/feature patches in our base packages.
I want to push those patches to trinity after doing a review with trinity contributors about their upstreamability.
And then I really want to switch to Trinity KDE in Pardus Corporate 2 as this will be a long-term supported release which should a have a maintained desktop environment.
Right now I started to prepare packages for the dependencies.
I'm waiting for your co-operation to make things better.
--- Ozan Çağlayan TUBITAK/UEKAE - Pardus Linux http://www.pardus.org.tr/eng
Hi,
Pardus is a Linux distribution funded and developed by the Turkish Government. We're planning to release a Corporate version - Pardus Corporate 2 - which is based on KDE 3.5.
We've been maintaining KDE 3.5 for a very long time so we have a lot of bugfix/feature patches in our base packages.
I want to push those patches to trinity after doing a review with trinity contributors about their upstreamability.
And then I really want to switch to Trinity KDE in Pardus Corporate 2 as this will be a long-term supported release which should a have a maintained desktop environment.
Right now I started to prepare packages for the dependencies.
I'm waiting for your co-operation to make things better.
This sounds like a great idea! I am not sure how you would like to slipstream the bugfixes into Trinity, as equivalent patches may have already been applied. Suggestions here are welcome.
The main criteria for including patches into the Trinity project is that a.) No existing user-visible functionality is removed b.) If new functionality is added or the user interface is altered that said functionality or UI changes can be deactivated by the end user through a GUI configuration option c.) The patches must be maintainable; i.e. clearly understandable by a third party and adhering to all rules of the programming language in use.
Thanks!
Timothy Pearson Trinity Desktop Project
I remember trying Pardus a while back, but didn't get much into it. It didn't leave a bad impression though, and it's nice to see a government leaning toward something that actually works (you guys may need to talk to our USA gov). Once you guys start pushing some patches around, I'd be game for testing, though with limited Internet, I may be a bit slow.
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?
Best regards, Tiago
On Fri, Dec 10, 2010 at 8:47 PM, Kristopher Gamrat pikidalto@gmail.comwrote:
I remember trying Pardus a while back, but didn't get much into it. It didn't leave a bad impression though, and it's nice to see a government leaning toward something that actually works (you guys may need to talk to our USA gov). Once you guys start pushing some patches around, I'd be game for testing, though with limited Internet, I may be a bit slow.
-- Kris "Piki" Ark Linux Webmaster Wannabe Ark Linux packager
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?
Thanks, Ozan Caglayan
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?
Correct,
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
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?
http://mirror2.quickbuild.pearsoncomputing.net/trinity/releases/3.5.12/kde-i...
This is the only tarball that I can see in the website but I think it would be better to distribute every i18n tarball separately as packagers are preparing separate i18n packages for their distro.
Or I can't find the separate tarballs :)
Thanks,
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?
http://mirror2.quickbuild.pearsoncomputing.net/trinity/releases/3.5.12/kde-i...
This is the only tarball that I can see in the website but I think it would be better to distribute every i18n tarball separately as packagers are preparing separate i18n packages for their distro.
Or I can't find the separate tarballs :)
OK, I see what you mean now. The separate tarballs are only available in SVN (see here http://websvn.kde.org/branches/trinity/kde-i18n/); for future releases they should be available separately as they are in SVN.
Thanks for bringing this to my attention!
Tim
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
On Saturday 11 December 2010 12:56:59 Ozan Çağlayan 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.
How did we resolve the problem with imlib?
It seems that kuickshow (which is needed for and kde3-digikam) require imlib, and do not build with imlib2. And imlib require gtk-devel and does not build with gtk2-devel...
-
Ilya Chernykh -
Kristopher Gamrat -
Ozan Çağlayan -
Tiago Marques -
Timothy Pearson