PackageKit is quite a complicated code base. As with all my projects, there is a substantial self check framework that’s designed to catch bugs and regressions before we push releases. This was something enforced by my previous employer, but I’m sure it’s a good idea for any non-trivial code base, and it’s something I’ll continue to do.
The tests are all injecting valid and invalid input and then testing if the code does the right thing. This works really well for the daemon and the library, but does not work well for the GUI applications that need a full GUI framework.
I’ve tried dogtail, but I’m finding it hard to use, and really wanted something I could integrate with my existing system in C. Do any of you hackers recommend anything in particular or should I persist with dogtail? So far it’s looking best of the bunch.
What gpk-application looks like with collection support
A collection is a metapackage that can represent a group, where the package mapping is done inside the backend. It is not like a catalog where an external file provides a meta-group. This enables the “group install” and “group remove” functionality people have been requesting since version 0.1.0, without get another abstract group mapping or extra API to support.
I’ve made a few changes in the daemon to properly support this new type, and in the yum backend Tim Lauridsen has added support using the comps group mapping. Mike Langlie has drawn us some great icons, and Anders F Björklund implemented collections for smart, and helped us with the design process. The extra type should be trivial to add to other backends too.
We added the feature in just a few hours of hacking, as everyone was working together. I’m amazed at how people work together so well all over the globe, in different timezones and with different work priorities – thanks guys.
Owen Taylor has been rocking recently. In the 0.3.x releases there’s an optional packagekit-plugin package that is a standard Mozilla plugin. It works in Firefox and Epiphany and looks something like this:
Test page shipped with PackageKit
It’s actually pretty easy to build a website that wants to install something new or run an application that is already installed.
The actual html you need is something like this:
<object type="application/x-packagekit-plugin" width="500" height="200" class="packagekit-plugin">
<param name="displayname" value="KStars"/>
<param name="packagenames" value="kdeedu kde4edu"/>
<param name="desktopnames" value="kstars"/>
You can omit displayname and desktopnames if you wish, as PackageKit can query the backend and fill in the blanks. The packagenames are queried until PackageKit finds one that matches on your system.
I’m also thinking about adding the application icon in the box as common applications usually have standard icons that PackageKit already uses for other stuff.
Of course, because this uses PackageKit, it’ll work on any distro. If you want to improve the look of the plugin or add some extra features, jump on the mailing list and give ideas. Feedback welcome.
I’ve been asking users with PackageKit bugs to report them upstream on the mailing list or in bugzilla, explaining what common error messages mean, and how to fix other problems.
This, it turns out isn’t what the forums are for. I guess it’s just for uniformed users telling less informed users how to “fix” things. My mistake.
I won’t be even reading the forums anymore, and consider the couple of hours I spent on the forums answering questions and educating users about PackageKit wasted.
These are all the posts I’ve made on the forum if you want to check any of my messages. A few of them are pretty blunt, but the personal critique of my skills as a programmer and PackageKit is pretty blunt too (especially by a “Community Manager“).
If anyone is using the latest Fedora 9 kernel on a T61, and their audio device has disappeared, worry not. It’s a kernel regression and is fixed upstream, and should be fixed when we get the next kernel update out.
The entire purpose of PackageKit is to abstract out all the uninteresting packaging formats and tools into a coherent API that can be used by cool applications and tools in a cross distribution and architecture way.
Of course, this is limited by the distribution guys putting in the effort writing PackageKit backends for their system, packaging it up into packages, and then deploying it in new distributions to hapless users.
So far, we have quite a few distributions shipping PackageKit by default, and there’s every indication that a large majority will be shipping PK by the end of the year. Recently I’ve been very impressed with the work of Sebastian Heinlein integrating PK with APT. It’s been pretty difficult, as he’s been patching (rewriting?) chunks of python-apt so that the PackageKit API can be completed. For SMART, Anders F Bjorklund has also been writing huge chunks of code, which is also great.
Screenshot of some of the tools on Ubuntu (Copyright Sebastian Heinlein)
You can see how the other distributions are doing here.
Bad Behavior has blocked 2769 access attempts in the last 7 days.