Linked by Thom Holwerda on Wed 25th Jun 2008 22:31 UTC, submitted by Rahul
Linux Earlier this week, we reported on the Berlin Packaging API, an effort to consolidate the various different packaging formats and managers in the Linux world. Many compared this new effort to PackageKit, and today is running an article detailing what PackageKit exactly is, with a few quotes from the project's lead developer, Richard Hughes.
Thread beginning with comment 320159
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: so...
by axel on Thu 26th Jun 2008 01:20 UTC in reply to "RE[2]: so..."
Member since:

PackageKit at least provides some hope that a unified UI can be used.

not really though. I mean it's not like there was anyone stopping people from porting the gui portion of synaptic or yum to different packagemanagers or heck porting packagmanagers to different package formats see apt-rpm, hell pclinuxos is rpm based and uses synaptic.

its still only unified if everyone ports packagekit to their packagemanager (pacman, portage, ports, msi, pkg etc) AND sticks to the "official" packagekit UI- which as it doesn't support debconf, or repo management, and i suspect ebuilds are right out- seems unlikely.

Reply Parent Score: 1

RE[4]: so...
by Rahul on Thu 26th Jun 2008 01:44 in reply to "RE[3]: so..."
Rahul Member since:

Porting an existing gui is a mess in many cases. has a presentation detailing the problems. Also there is nothing stopping people from running the PackageKit GUI and having their native package manager gui installed in parallel for more advanced tasks. That is the approach used by many distributions. Note that ebuilds are getting to be a supported backend via a Google SoC project

Fedora and Foresight Linux already include PackageKit by default and nearly all the mainstream distribution are going to do it by the next version.

Reply Parent Score: 2