Hi FinalRebel. From the direction of the discussion in this thread it seems to me that the easiest option for you will be to wait for Slackware 13.0 :). It should come out soon, and there you'll find the UPGRADE.TXT file which tells how to upgrade to 13.0 from 12.2. You can use the version in the -current mirrors too but it's easier to have an iso/DVD around and doing everything at once. 13.0 will also come with a 64 bit version, so you may also consider doing a fresh Slackware64 install as well.

@FinalRebel
-----------
The direct answer. No pre built packages exist for KDE4 that are compatible with 12.2.
-----------
A the risk of stability and functionality of your system, you can install KDE4/QT4 from slackware-current.
-----------
There are QT4 build scripts located at slackbuilds.org. But that involves compiling and then building KDE from sources anyway.
-----------

My initial post was to warn you about the risk of messing things up if you attempt to only upgrade the package manager, QT, and KDE.

We warn you because most of your QT programs WILL NOT FUNCTION if you upgrade KDE4 which needs QT4.

If you 'NEED' KDE4, It is best to do a complete install of slackware-current or slackware 13.0 when it is out.

thanks all for the help.

Did you solve...?

Everyone else is beating around the bush with this, so I'll be a bit more direct.

You are certainly free to install -current packages on 12.2, but you need to be aware that it's COMPLETELY unsupported, STRONGLY discouraged, and generally stupid. There are certainly exceptions, but if you don't already know how to determine what the exceptions are and why they are exceptions, you don't even need to be aware that they exist.

-current is the DEVELOPMENT tree of Slackware, and it is often incompatible with the latest stable release, ESPECIALLY this close to a new stable release. In short, don't do it. If you do, you're on your own.

I prefer a new installation since I once had problems with (after) updating of libraries.

Markus

After you ran "slackpkg upgrade-all" and got 3 packages, xz is not one of them. You have to do that manually by "updating" slackpkg again with a new uncommented line in /etc/slacpkg/mirrors, then install xz by "slackpkg install xz" and then upgrade the whole shebang. No guarantee that this will be the whole of it;

Were I you I'd wait for 13.0 to come out, it will probably not be long before the world is ready for it.

Anybody know of a list somewhere to send people of things you should never pick and choose to upgrade if you don't know what you are doing?
Kernel
Tool Chain (gcc, binutils, etc.)
Python
QT
KDE (gnome)

There can never be such a list because what backwards compatibility is broken depends entirely on what libs get upgraded during the development cycle. For example if none of the libs (including qt) were upgraded from 12.2 -> 13.0 KDE4 would be usable on both cause it would be built linking on the same library versions.
That is a general rule and only exceptions are binary repackaged packages like firefox (only 32bit) or openoffice etc.

If you want to play safe stick to a stable release and only apply stuff in patches/