Kpackage makes no sense any longer.

[davetshave]

When I first started using Kpackage I was well impressed by the ease with which new software was added. It even seemed to put the links to the new software in to existing folders in the start menu in a logical way, really neat.

However I have been unable to get certain packages to install.

Take VIM for instance. I found the RPM on my install CD's and opened it in Kpackage. Then I try to install it. Everything goes fine, except it doesn't install it at all. All it does is place it in the structure with a cryptic red 'N' next to it instead of the normal symbol for an installed package.

I read the 'manual' (it took about 3 minutes) and it entirely failed to explain what these symbols are supposed to mean. Does anyone know what a big red "N" means, or a "U" for that matter? Even more interesting would be to hear how to smack Kpackage round the head so it just get's on and installs the package.

Interestingly enough when I installed the rpm from the command line it worked flawlessly. Makes me wonder why I bother with Kpackage at all. Anyone else noticed similar misbehaviour?

DaveTshave.

[colbec]

Gave up on kpackage some time ago, found that gnorpm did not load at all, went with rpmdrake, found that quite frequently it only loads half the database on first load, then disappears from the desktop but if I run it again the full db is there.

rpmdrake is helpful for intricate searches, otherwise simple installs, like your situation, are done from the command line, rpm -i ..... particularly if I know in advance which CD is needed.