I've been experimenting with Slackware-current with KDE. However, if I try to use
KPackage I get a pop-up telling me that SMART Package Manager is required.

I have been unable to locate the SMART Package Manager on the ISO that I am
using, and have been unable to locate it elsewhere.

Question: Where is SMART Package Manager?

There is a SlackBuild-script.
http://slackbuilds.org/repository/12.2/system/smart/

Slackware does not support the use of kpackage. You could say that the "smart" package was left out with a purpose.

Eric

As Eric stated, smart was intentionally omitted.

Thank you for your speedy replies. However, considering that KPackage has been supported in
previous versions of Slackware, why eliminate it now?

I had a play with this some time ago to try and get kpackage a little more functional with KDE4. I sometimes used it to see what's in a package in Slackware 12 and prior versions. With smart loaded it will load kpackage but looking at a package contents wont work for me so I gave up on it. As said, kpackage is not supported and works even less with KDE4 so I wouldn't bother if I were you.

I always use pkgtools for most package stuff but like to use kpackage to view what's installed,( when in KDE), and their contents. Looks like I won't be using kpackage at all now ! I'll now stick to the /var/log/packages/* files for browsing an installed package's contents - oh well !

psynot, if you are looking for a graphical package manager for Slackware, you might want to give GSlapt a try. (you can get it from http://jaos.org)

It has never been officially supported by Slackware. Quite the opposite, past versions have been known to screw up some files in /etc (most notably the /etc/rc.d/rc.inet1 script).

You are of course free to install a smart package and use kpackage, but you will not get support if things don't work.

Eric

slapt-get with gslapt works well for seeing what you have installed as it shows the version and everything needed if updating or upgrading.

Try webmin.

Search, install, remove, upgrade, list files installed by a package. It's actually quite powerful and useful.
http://img29.imageshack.us/img29/5700/snapshot4r.png (get info on a single file)
http://img16.imageshack.us/img16/5498/snapshot5jxo.png (interface)
http://img90.imageshack.us/img90/3023/snapshot7.png (package details)

Whoa!!!!!
I could really hose some stuff with that!!!
If I do,,,, I blame you!

@ Alien Bob

I have been using Slackware since v.10. I have always used KDE and KPackage and have
never had problems or incompatibilities. In other words, it has always worked perfectly for
me on both my current machine (Compaq SR1920NX with an Athlon 3500+) and on the machine I
owned previously (HP Pavilion 6640--500MHz.)

These are both plain vanilla, off-the-shelf machines, why is it that you have found problems
with it? I don't understand.

@psynot: Eric is not saying that it's bad or won't work.

I won't speak for him or for the Slackware team as a whole, but here's my take on it: I'd rather not see kpackage as it currently exists being used. It's quite limited in its functionality (with respect to Slackware packages - that doesn't imply a weakness in kpackage per se), and it expects to be able to do things that simply can't be done on a vanilla Slackware machine (show package dependencies and such). Many (newish) Slackware users might not be aware of this limitation, and as such they are prone to report bugs in kpackage. Lots of invalid bugs reported from users of a particular distribution can possibly lead to the upstream folks having a bad taste in their mouth about that distribution (recall Pidgin back around 11.0?).

I've been working with computers since 1969 and with electronics generally for a great deal longer. Please don't insult me by calling me a newbie.

@psynot: when you manage to find anywhere that I called you a newbie, then you can castigate me on a public forum. Since you can't, unless you misconstrue my statement from above, then you should just keep your piehole shut.