What I like in kpackage:
The search lets me step through results one at a time as opposed to
bringing up a whole list of matches. (This may be just a matter of
taste, but I figured out how much I liked it when I acidentally did a
search on nothing on RPMDrake which took a while to return nothing.
How? See below.)
Kpackage has the option to display all the packages available in a
single view as opposed to having to choose only the installed vs the
installable. Kpackage also lets me view packages that are updates to
what is already installed by selecting the appropriate tab. At a
glance, I can see what is new ("N"), updated ("U"), or installed (funky
RPM icon). Knowing what to update in RPMDrake requires watching for
update notices in places like MandrakeForum or Linux Today, or even
keeping an eye on my FTP mirroring logs (which is the only way to catch
an updated unsupported package).
Kpackage also appears to better handle "foreign" packaging types such as
Debian, Slackware, BSD, and kiss (whatever that is).
What I like about RPMDrake vs kpackage:
The seperate window showing my selected packages is nice. RPMDrake
knows dependancies to packages instead of just offering links to the
dependancies. Kpackage does make you do a little searching at times for
what provides some requirement as the links only exist if you've "seen"
the required package.
>From what I see in the Cooker version, there is an "Easy Updates" button
on RPMDrake. Perhaps that will provide what I get from the "Updated"
tab of kpackage. This button is definitely not present in the 8.0
version, though I hope it will be back-ported to help those who don't
know an easy way to pull up updated packages in RPMDrake.
I'm afraid I'm going to have to cut this list short. I'm spotting other
problems in cooker that I want to check for reports on.
Axalon wrote:
>
> On Sun, 8 Jul 2001, Digital Wokan wrote:
>
> > I know I'm not the only one receiving the following errors. Command line rpm
> > commands work, and rpmdrake starts, but any attempts to start kpackage or
> > gnorpm result in the same error. Does this have something to do with the
> > upgrade to rpm-4.0.3 or something? And if so, is there someone working on a
>
> Yes
>
> > fix for them yet?
>
> No, atleast i doubt it. Being that i've had to write updates for gnomrpm
> due to rpm changes, it's much less painfull to just let the actual creator
> make the updates needed when rpm changes.
>
> > [root@beast cookrpms]# kpackage
> > kpackage: error while loading shared libraries: /usr/lib/librpm.so.0:
> > undefined
> > symbol: fpHashFunction
> > [root@beast cookrpms]# gnorpm
> > gnorpm: error while loading shared libraries: /usr/lib/librpm.so.0: undefined
> > symbol: fpHashFunction
>
> Perhaps you should make a list of what these two do that rpmdrake doesn't
> and submit them for inclusion in rpmdrake.
>
> --
> --Axalon
