Re: KPackageKit
sorry for the delay, actually i said that sending in this email could lead to
a delay or a lost msg...
>I may be wrong but from the PackageKit that Richard Hughes gave at
>Guademy 2008 I had the impression PackageKit and KPackage complement
>each other, i. e. instead of having the package management code in
>KPackage, make KPackage just a cool GUI around the PackageKit DBUS
>API.
Well, KPackageKit IS almost a nice GUI frontend to PackageKit.
>Why did you start a new development instead of porting KPackage
>to use PackageKit? (Please note I'm not saying KPackageKit is a bad
>idea, in fact I like it and I'd like to see more KDE tools ported to
>fd.o helper tools such as system-tools-backends )
Why not use KPackage code, simple:
Every piece of code there would be useless to me,
KPackage has the code to actually install things on itself
i know it uses smart but anyway i had different ideas that would
just don't fit in there.
The KPackageKit is all built on mudules
so you go to system settings to change packages,
there are too different stuff.
As the name says KPackageKIT is for Packagekit ONLY,
i don't want it to be used in a specifc package manager
package manager specifc stuff should be discussed in packagekit
development, and that will reflect gnome-packagekit and KPackageKit.
think this like an official gui to PK for kde, if you want KPackage to be
able to use PK it's very simple just use libpackagekik-qt ;)
see you.
--
View this message in context: http://www.nabble.com/KPackageKit-tp17247353p17762959.html
Sent from the kde-devel mailing list archive at Nabble.com.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<