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.
So, howdy Nixers'n'Nixettes, this one sounds simple:
How would you switch to KDE4.2 on a 12.2 production machine that heavily relies on KDEPIM, Kate, Konqueror. (but nothing else actually, I run Enlightenment DR16 as WM).
-current is enabled, I can "see" kdebase-runtime-4.2.0-i486-1 and kdebase-workspace-4.2.0-i486-1.
I understand that the KDE 4.2.0 packages for -current are compatible with -stable. My question is: What may I expect for the future? Will there be patches the preserve this compatibility? Or will I be forced to either switch (i. e. "upgrade") to -current or remove KDE 4.2.0 some day?
Because I am conservative on the one hand, but since I saw KDE 4.2 on OpenSuSE I want it on Slackware.
The answer is in the Changelog for Slackware Current. For now it is compatible but there is no guarantee that it will stay so. But wait till Eric comes back, he knows about that as he is the packages' author
The answer is in the Changelog for Slackware Current. For now it is compatible but there is no guarantee that it will stay so. But wait till Eric comes back, he knows about that as he is the packages' author
Meanwhile I am happy with Fluxbox
Yes, I saw the the changelog. Which actually is the reason why I ask this question.
I'd grab KDE 4.2.0 now, if I could be sure that it will be compatible with Slackware 12.2 at least until the next Slackware release (12.3 or 13.0, who knows). This means, that I would like to get security patches for KDE 4.2.0 on Slackware 12.2, too. I just would like to avoid running -current, for a while, only to have KDE 4.2.0. Worst thing would be having to "downgrade" to KDE 3.5 in a few weeks.
Yes, I saw the the changelog. Which actually is the reason why I ask this question.
I'd grab KDE 4.2.0 now, if I could be sure that it will be compatible with Slackware 12.2 at least until the next Slackware release (12.3 or 13.0, who knows). This means, that I would like to get security patches for KDE 4.2.0 on Slackware 12.2, too. I just would like to avoid running -current, for a while, only to have KDE 4.2.0. Worst thing would be having to "downgrade" to KDE 3.5 in a few weeks.
gargamel
If you grab thew KDE 4.2 packages from the slackware-current tree and install them on Slackware 12.2, it will work. But do not expect to see updates to KDE 4.2.x packages that are specifically meant to work on Slackware 12.2. The fact that they do now, is just your luck. When we see the next update to gcc and glibc in slackware-current, this will likely be the point after which new slackware-current packages will be incompatible with Slackware 12.2.
If you want to use KDE 4.x and keep using it, you are going to have to upgrade your Slackware in the end. Period.
Eric
Last edited by Alien Bob; 01-30-2009 at 04:46 PM.
Reason: Changed 12.0 to 12.2 .... thanks gargamel for noticing
If you grab thew KDE 4.2 packages from the slackware-current tree and install them on Slackware 12.0, it will work. But do not expect to see updates to KDE 4.2.x packages that are specifically meant to work on Slackware 12.0. The fact that they do now, is just your luck. When we see the next update to gcc and glibc in slackware-current, this will likely be the point after which new slackware-current packages will be incompatible with Slackware 12.0.
If you want to use KDE 4.x and keep using it, you are going to have to upgrade your Slackware in the end. Period.
Eric
Thanks, Eric, for clarifying this. Just to make sure: When you refer to Slackware 12.0, this includes 12.2, too, right?
Hm..... I meant 12.2 where I wrote 12.0 actually. My apologies for not checking what I typed before I hit "Post". The KDE 4.2 packages in slackware-current are incompatible with Slackware 12.0.
Yep, I "chicken" out too: Read the Readme in the FTP download for 4.2, and re-read this thread: the title says "production".
I will happily jump to Slack 13 asap, but feel not that keen to stay on the -current repos and see stuff starts breaking down, or loose whatever extra app I compiled myself that relies on qt3.
I am not saying troubles described in the readme or explained here cannot be (easily) overcome, just that I, well, feel like not doing it now. Much thanks AlienBob and Didier for the accurate answers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.