Ubuntu QA:
BlogBrainstorm
Log in
Ubuntu QA
The Ubuntu community has contributed 12232 ideas, 57574 comments, 1174524 votes

Idea #64: Use packagekit to improve standardization



bug This idea was marked as being in development the 4 June 08. Target release: Ubuntu 8.10 Intrepid Ibex.
up
317
down
Written by rainforest12 the 28 Feb 08 at 16:16. Category: System.
Related to: Nothing/Others. Status: In development
Description
Hi guys!
packagekit gets more and more attraction, i don't think that i have to explain it here, someone who knows this page knows also packagekit and its possibilities i.e. share package discribtions & news, openoffice.org can use it for the installation from additional packages/art; automatic printer driver download from lsb-site and so on...

more here:
http://packagekit.org/
and a really hot presentation from fosdem08:
http://people.freedesktop.org/~hughsient/public/introduction-to-packagekit.pdf

Tags: (none)


Developer comments
The use of PackageKit for Ubuntu is targeted for the Intrepid Ibex! See the attached blueprint for more informations.


Attachments


Duplicates


Comments
suzzlo wrote on the 28 Feb 08 at 17:55
second link doesn't work :-(

suzzlo wrote on the 28 Feb 08 at 17:57
It work! sorry about previous comment.

v1ncent wrote on the 29 Feb 08 at 00:21
ABSOLUTELY! PackageKit it's awesome .
Please people, vote for this, because we doesn't have an universal installer, and that's OK, bt not so good.

PackageKit give us a wonderful solution to this, we could use yum, conary, apt-get, box, zypp, emerge and
other backends (maybe in the future SuSe metapackage, klik and others).

We really need to support projects like this!

mguymon wrote on the 29 Feb 08 at 02:35
A bold project idea and would be great to see it actually work, but I am worried it might tread in murky waters. It would be an interesting to emerge Apache with dependencies on an apt'd PHP deb using a yum'd xml lib from a rpm. I imagine things would be murky when you have to figure out dependencies spanning different methods of dependency management.

sparc128 wrote on the 29 Feb 08 at 05:03
Seems to me Fedora/Centos needs this more than Ubuntu right now but it does have some good layouts so I think it would help relieve resources on all distro's if they standardized on it.

azrael wrote on the 29 Feb 08 at 12:54
There is already a spec about it:
https://blueprints.launchpad.net/ubuntu/+spec/package-kit

madjr wrote on the 15 Mar 08 at 05:09
foresight linux is using it now
http://www.foresightlinux.org/news.html

it's also the first distro with gnome 2.22 would be great to give it a test drive :)

mkantor1 wrote on the 26 Mar 08 at 18:08
Fedora 9 is also using it:
http://www.redhat.com/archives/fedora-announce-list/2008-March/msg00011.html

We should keep an eye on these distos and learn from their experiences with PackageKit.

fluteflute wrote on the 21 Apr 08 at 18:12
Currently PackageKit is nect to useless on Debian/Ubuntu because it does not support APT. Look at the APT column: http://www.packagekit.org/pk-faq.html#how-complete

Ferdil wrote on the 4 May 08 at 13:18
NOW it doesn't support it completely. In the near future it will.

Vadim P. wrote on the 6 Jun 08 at 21:28
I hope the packagekit guys make apt support by 8.10

Ralf.Nieuwenhuijsen wrote on the 8 Jun 08 at 11:29
No!

Ubuntu already has add/remove.
Package kit is the same, except is user interface sucks more.

It will be a huge regression in usability if add/remove is replaced with packagekit. I've already submitted a bug to the packageKit developers about the user-interface not having a specific target group in mind and the interface being too scary for novice users. ("stop scaring my mom").

There is so much wrong with it, this is just a first list:

- it prominently uses the package-names rather human names.
- it does not use icons from the packages.
- it does visually distinguish between packages installed and those not installed
- there is no way to just get a list of installed software
- it does not search as we type
- the categories are not related to the menu

It's as scary as synaptic, yet as weak as add/remove.

Honestly, its a piece of crap. Ubuntu has the user-interface for package management already perfected.

Replacing add/remove and synaptic with packageKit is unexceptable. I'm pretty sure, everybody is going to talk about how much it sucks and how its a regression.

Not the type of people that come to brainstorm. But the majority of the users will stop installing software themselves. PackageKIT is so not ready. (and until it's a complete duplicate of add/remove, it won't be).

Please don't do this!

Nazo wrote on the 8 Jun 08 at 13:34
Noooooooo!

Vadim P. wrote on the 8 Jun 08 at 14:59
PackageKit will not replace apt-get, I think. It's like an "addon" to apt-get, and it makes people who want to distribute software on linux lives much easier.

unimatrix wrote on the 9 Jun 08 at 14:30
Everybody who disagrees with this is just retarded. Every usability problem with PackageKit will be fixed, or is already being worked upon.
PackageKit is amazing at insuring much better standardization. It's an absolute must!
+1

Auzy wrote on the 9 Jun 08 at 15:15
Vadim is right..

------SNIP-----------
PackageKit is a system designed to make installing and updating software on your computer easier. The primary design goal is to unify all the software graphical tools used in different distributions, and use some of the latest technology like PolicyKit to make the process suck less.

The actual nuts-and-bolts distro tool (yum, apt, conary, etc) is used by PackageKit using compiled and scripted helpers. PackageKit isn't meant to replace these tools, instead providing a common set of abstractions that can be used by standard GUI and text mode package managers.

PackageKit itself is a system activated daemon called packagekitd. Being system activated means that it's only being run when the user is using a text mode or graphical tool, and quits when it's no longer being used. This means we don't delay the boot sequence or session startup and don't consume memory when not being used.
--------------END SNIP-------------

Ralf.Nieuwenhuijsen wrote on the 9 Jun 08 at 23:16
I'm not talking about the nuts-and-bolts.

I'm talking about the actual interface of the packageKit gui's.

THEY ARE HORRIBLE.

The intentions are all nice, and perhaps someday the gui will be acceptable enough to ship by default. But until then Ubuntu should stick with its guns.

PackageKit gui's is not modelled after add/remove in Ubuntu. It looks more like an bad mockup where no thought went it, and the HIG was completely ignored.

If the authors of PackageKit had any intention of getting it right, they would have started with Ubuntu's add/remove interface as a reference point. Instead they created something with a UI from the stone-ages.

I still can't imagine what they were thinking when they designing the GUI for it. I'm not even sure they were thinking.

Replacing add/remove with packageKit is completely unacceptable. Anyone that ever worked with both add/remove and packageKit should be able to verify that.

Auzy wrote on the 10 Jun 08 at 02:43
Yeah, they clearly state that the packagekit gui is under development. But there is no reason why we couldn't patch synaptic to use packagekit as the backend i'd imagine

natureflow wrote on the 15 Jun 08 at 15:31
You'll may use gnome-app-install, update-manager, etc as frontend. You do not need to use these demo frontends!

derubermensch wrote on the 18 Jul 08 at 09:05
No, Ralf is right. I just finished a Fedora 9 session, and MY GOD PackageKit is horrible!

Don't let hype override firm design principles, PackageKit is NOT ready, both for general use and the apt PM

Auzy wrote on the 18 Jul 08 at 09:25
Are you speaking about the interface or the integration though derubermensch? Because technically, I'd imagine it should be possible to convert synaptic to exclusively use packagekit.

derubermensch wrote on the 18 Jul 08 at 19:04
The graphical interface is useless. I also don't see the point of PackageKit when aptitude, apt-get, synaptic, and add/remove are perfectly good and work now.

What do you mean by 'convert Synaptic to exclusively use packagekit'? Synaptic is already a graphical abstraction of apt, why would you put another abstraction under it? Am I missing something?

Auzy wrote on the 19 Jul 08 at 01:54
Ok, thats maybe why you don't understand the benefits. Packagekit is a standardised means of accessing any package control system. So its no longer necessary to design programs for RPM, APT, or whatever. With Packagekit, it should be possible to program your packaging program, without worrying about the backend (it will work with APT, RPM, whatever).


Its more then just a frontend. Its the backend that does all the magic, and makes it possible for developers to create universal packaging systems.

gruntsters wrote on the 30 Jul 08 at 11:28
At present there are no benefits to PackageKit. It isn't even ready for alpha testing. They threw it into Fedora 9 at the last minute, and its abhorrent. I've installed Fedora 9 on 4 machines and it failed to do anything but tell you that you have updates.

I've never been so shocked at such a lack of competence in software developement in my entire life.

All of you Ubuntu users be very afraid when PackageKit comes your way if its handled like they did in Fedora.

At present, most linux forums and wikis that have walk thrus for installing software and etc. for Fedora 9 tell you to first do a yum remove PackageKit.

Vadim P. wrote on the 30 Jul 08 at 19:05
Surely it can improve in 6 months?

And this won't be the main method of installation... just support for it for now. apt will still be the main

coolen wrote on the 7 Aug 08 at 14:03
There's nothing saying you have to use PackageKit's frontends. Synaptic certainly won't. The features it uses are simplly out of PK's scope.

We could always build our own. That's no problem.

The important thing, in my opinion, is allowing developers to pull in dependancies with minimal user interaction. If they can depend on PK being there, they can simply call out to it, ask for a package (or a package providing a certain file), and the requested functionality is in place.

One possible use case would be Totem/Rhythmbox. Code could be added upstream to pull in restricted codecs. All Ubuntu would need to do is provide them.


Post your comment