Slackware 13.0 with KDE 3.5.10?
in [Slackware]
|
Prev: useradd, upgrading Feunster
Next: Qemu help
From: Tuxedo on 25 Dec 2009 10:08 Hi, I recently installed Slackware 13.0 on a notebook and everything worked more or less as expected, except for direct graphic rendering with my integrated Intel card. This has been the case for most major up-to-date distros I tested on the somewhat old notebook, namely a Samsung Q25. That said, a Knoppix CD with its superior HW-detection came to rescue: I simply copied the entire xorg.conf file from within a live Knoppix session over the version Slackware had generated and all graphics thereafter worked brilliantly! After testing Slackware 13.0 with KDE 4.2.4 for a while I found I missed KDE 3.5. I personally think the old GUI is more user-friendly. As such, I uninstalled Slackware 13.0 and reinstalled the earlier Slackware 12.2, which of course comes with KDE 3.5.10. However, I guess the better solution would be to install the latest Slackware 13.0 initially without KDE and thereafter manually install KDE 3.5.10. I understand there are no binary packages for Slackware (http:// kde.org/info/3.5.10.php). Not having manually installed a windows manager ever before, I have a subjective question: Is it a complicated affair to install KDE 3.5.10 on Slackware? Will it even work on Slackware 13.0? Or would I be better off to stick with Slackware 12.2? If so, what important features would I be missing? Eg. the 'speaking' kernel sounds like a potentially useful feature which I believe isn't an available out-of-the-box option in 12.2. Many thanks for any tips! Tuxedo
From: Tuxedo on 25 Dec 2009 11:40 On Dec 25, 4:08 pm, I wrote: > If so, what important features would I be missing? Eg. the 'speaking' > kernel sounds like a potentially useful feature which I believe isn't > an available out-of-the-box option in 12.2. In fact my current 12.2 Slackware installation appears to have 'Speak Text' built into Konqueror. Only KTTS has not been configured. But for some reason adding a voice does not seem to work. Must I install the 'festival' back-end first? I can't find this in KPackage. However, kdeaccessibility-3.5.10-i48 exists on the system.
From: Henrik Carlqvist on 25 Dec 2009 14:55 Tuxedo <tuxedo(a)mailinator.com> wrote: > I missed KDE 3.5. I personally think the old GUI is more user-friendly. > As such, I uninstalled Slackware 13.0 and reinstalled the earlier > Slackware 12.2, which of course comes with KDE 3.5.10. However, I guess > the better solution would be to install the latest Slackware 13.0 > initially without KDE and thereafter manually install KDE 3.5.10. First question: Why would you prefer Slackware 13.0 instead of Slackware 12.2? If you don't know the answer and already know an answer to why you would prefer Slackware 12.2 the easiest path is probably to stick with Slackware 12.2 and keep your Slackware 12.2 up to date with patch packages. If Slackware 13.0 has some more package that you really like it is probably a lot easier to compile that package for Slackware 12.2 than to compile KDE 3 for Slackware 13. So my advice for you right now is to stick with Slackware 12.2. One day KDE 4 will have improved so much that it will have some features that you really envy. That day you will be willing to learn the new look and feel of the GUI to gain access to those new features and once you have learned how to use the new version you will probably find even more new features that you will like but also miss some old lost features. That day might be when Slackware 13.1 is released or it might be when Slackware 17.3 is released. You choose when to upgrade, if you don't think you have a good reason to upgrade you shouldn't upgrade. regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost
From: Eric Hameleers on 25 Dec 2009 18:17 Tuxedo schreef: > After testing Slackware 13.0 with KDE 4.2.4 for a while I found I > missed KDE 3.5. I personally think the old GUI is more user-friendly. > As such, I uninstalled Slackware 13.0 and reinstalled the earlier > Slackware 12.2, which of course comes with KDE 3.5.10. However, I > guess the better solution would be to install the latest Slackware > 13.0 initially without KDE and thereafter manually install KDE 3.5.10. > > I understand there are no binary packages for Slackware (http:// > kde.org/info/3.5.10.php). Not having manually installed a windows > manager ever before, I have a subjective question: Is it a complicated > affair to install KDE 3.5.10 on Slackware? Will it even work on > Slackware 13.0? Or would I be better off to stick with Slackware 12.2? > If so, what important features would I be missing? Eg. the 'speaking' > kernel sounds like a potentially useful feature which I believe isn't > an available out-of-the-box option in 12.2. Easy... download and install these packages which Pat made for people like you who are not ready for KDE4: http://slackware.osuosl.org/unsupported/kde-3.5.10-for-slack13.0/ They are compiled on Slackware 13.0. Their status is "unsupported", meaning there is no guarantee they will work on slackware-current or any future stable release. Eric
From: Henrik Carlqvist on 26 Dec 2009 06:39
Eric Hameleers <eric1(a)sox.homeip.net> wrote: > Their status is "unsupported", meaning there is no guarantee they will > work on slackware-current or any future stable release. What about security patches? I suppose that unsupported packages will not get any security patches? On the other hand as there is no longer any upstream support for kde 3 there will probably not be much patches for the official kde 3 packates in earlier versions of Slackware either. regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost |