Sorry, one more question for today, KDE 3.4, which one?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Sorry, one more question for today, KDE 3.4, which one?
Ok, I upgraded the stock KDE in Slack 10.1 with the one from Linuxpackage, made by Jim Simmons.
I noticed there is one on kde.org also. Made by Jean-Christophe Fargette. I used his packages before and they worked well.
I'm heving some problems with Jim's KDE though.
Not a contest, I respect and admire both packagers.
Just asking if someone tried both sets of KDE packages and how they compare, before I download the ones from kde.org.
Thanks.
I tried Simmons' before Pat's were released and they seemed fine but had too many deps for my taste. Replaced them with Pat's which also seem fine. Plus, whatever was gobbling my memory seems (slightly) better with Pat's. Dunno about the other set.
But there could be all kinds of stuff wrong and I wouldn't notice. Not a desktop user normally. Gotta admit, though, this KDE isn't too shabby.
When upgrading from KDE 3.3 to 3.4, do you recommend to remove all KDE packages first, then install the new KDE packages from slackware-current, or simply do a pkg-upgrade while in init 3 ?
Dunno - I've never kept KDE on long enough to upgrade, As far as switching sets, I kind of instinctively removed all the packages and then 'installpkg'ed the official ones without thinking about it. I mean, there were a couple-three packages in the js set that aren't in the 'pjv' set and would have to be removed anyway. But if I was regularly running official Slack KDE, I don't suppose it would make much difference and would probably just upgrade.
Definetly removing all the old KDE packages would be a really really really good idea! Otherwise your system will be a mess since both kde 3.3 and 3.4 write to the same /opt/kde heirarchy.
Originally posted by mdarby I used the Slackware packages off of KDE.org with no problems.
Thanks mdarby, I think I'll give them a try.
The install from Linuxpackages is giving me some errors, like crashing kicker and "Can't fine Dr. Kongi".
Other than that it's working fine.
Memory consumption is almost 90Mb on my system. With fluxbox it's about 40Mb. Quite a difference.
I haven't noticed any difference between LinuxPackages, KDE, and Pat V's KDE yet, except that Pat V's version doesn't include widgets (which I use as minimal eye candy), unless you install kdeaddons. This probably won't make any difference unless you want the widgets, but you don't want to install the extra stuff in kdeaddons. Of course, this is better for you if you just want a barebones KDE (with kdebase and kdelibs). The official KDE, I believe, has those widgets in either base or libs. I'm not sure about LinuxPackages.
That said, I'm sticking with Pat V's version, because I believe that to be the most stable. They're probably all very similar in that regard, but all else equal, I'll trust Pat V.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.