SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
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 !
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?).
@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.